On Wed, Feb 19, 2020 at 11:55 PM Sage Gerard <s...@sagegerard.com> wrote:
> I'm very much in favor of interoperability and am happy to work in that > direction. Does this imply that we need a #lang for each highlighting > target? With my approach, yes, but note that technically, the #lang doesn't need to be functional. The whole module could just expand into a raising of a runtime exception "not implemented". I'm not sure that in practice this is a good idea though. > What happens if you want to highlight code mixtures? Some snippets of > interest to me can include Javascript, Markdown, CSS, HTML and Racket all > within 20 lines. > Then the color lexer would need to be context-sensitive and knows when to switch its lexing mode. Note that this is not a problem due to this approach. Any other approaches would have the same problem. It would be cool if there's a way to annotate code with `#reader` at the meta level, which would make this problem much easier... -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CADcuegs-76-meLv7Lmr7enGy47fUqGeJChwq%2B%2B9Xbk7b%2Bz6GgQ%40mail.gmail.com.
