Re: Problems with syntax coloring a #lang

Am I right in inferring this is a lang you made and not a lang that
you'd like to report a bug about?

The symptoms you're seeing are generally bugs in the results of the
lexing function. It can be hard to get those right and the colorer
calls into your lang's reader in ways that you might not have realized
you should test.

Are you using the lexer-contract? Sometimes that can help you find the
input to your lexer that is doesn't work on.

Robby

On Tue, Feb 12, 2019 at 7:06 PM Chris GauthierDickey <[email protected]> wrote:
>
> Hi!
>
> I seem to have some weird behavior with syntax coloring a #lang. Sometimes it seems to think particular words that are normally correctly colored are errors.
>
> For example, if I'm starting to type a keyword, it's coloring it red (which it should), but when I complete the word, it doesn't re-color it the right color. Or if I intentionally delete a character and put it back in the middle of a properly colored section, some of the letters switch to the wrong color and don't switch back.
>
> If I tell racket to reload the #lang extensions, it goes and colors the buffer properly.
>
> I know that's not much to go on, but being that it's dynamically loaded by DrRacket, I'm having some problems debugging it!
>
> Thanks!
> Chris
>
>
> --
> 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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
> For more options, visit https://groups.google.com/d/optout.

-- 
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+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
For more options, visit https://groups.google.com/d/optout.