OK. Yes, I can reproduce. I had an extra commit from halfway through the next section which adds variables to the lexer. If I roll that out, then the 80% red 20% black thing sticks. If I change the no-color line to symbol, then it does redraw properly. Is there a “normal-but-not-no-color” value? I don’t see where drracket’s color semantics are documented

OK. I used ag and dug up syntax-color module and decided a fair default was other and it seems to have fixed it… I’ll send that as feedback to BR

So far when I’m building a fresh amd64 binary on my Windows machine using nmake win32-in-place it fails with either error nmake : fatal error U1077: 'racket/racket.EXE' : return code '0xc0000005' or nmake : fatal error U1077: 'racket/racket.EXE' : return code '0xc0000374' Googling those error codes tell me that it appears to be a memory corruption issue.

I tried doing build based off just the master branch without my changes merged and also a fresh build after doing a checkout of the v6.9 tag. I still get failing builds so I think this is something specific to my machine. I don’t know yet what’s wrong, I was able to build from the v6.9 codebase without issues at least a month ago.

I’ll give this another try when I have access to a different Windows machine. Are you satisfied with the most recent PR commit push?

@abmclin yes, I’ll push them, thanks!