<br> <div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm not sure if that's the best thing, but<br> the reason I did it that was was to avoid colors flashing around, as<br> the check syntax information comes and goes as you edit the buffer.<br></blockquote><div><br>Ah yes, there might be this problem indeed.<br>Maybe it could be possible to keep a "partial" state of the syntax checker, and only discard the parts that are being edited, until the document can be checked entirely, possibly with a warning at the bottom right saying that the syntax checker is not currently in sync.<br> That would help for the contract coloring as well as for the identifier information rectangle, but I'm not sure this is easy to implement.<br><br>Laurent<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> Robby<br> <div><div class="h5"><br> On Sun, Nov 11, 2012 at 8:57 AM, Laurent <<a href="mailto:laurent.orseau@gmail.com">laurent.orseau@gmail.com</a>> wrote:<br> > Hi,<br> ><br> > Starting my Xmas wish list:<br> > In case some developer doesn't know what to do (sure...), I think it would<br> > be visually quite helpful if contracts could be syntax-colored, for example<br> > in lighter blue. That would help quickly distinguish between the actual code<br> > and the debugging code.<br> ><br> > Thanks :)<br> > Laurent<br> ><br> </div></div>> ____________________<br> > Racket Users list:<br> > <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br> ><br> </blockquote></div><br></div>