<br><br><div class="gmail_quote">On Wed, Dec 8, 2010 at 3:56 PM, Ken G. Brown <span dir="ltr"><<a href="mailto:kbrown@mac.com">kbrown@mac.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">At 12:07 AM +0100 12/9/10, Levente Uzonyi apparently wrote:<br>
>On Wed, 8 Dec 2010, Ken G. Brown wrote:<br>
><br>
>>Thx.<br>
>>I'm wondering if there might be some way for the syntax highlighting to be made to reset itself instead of giving up completely after a syntax error and everything after that doesn't work at all?<br>
>>eg. the quote character? The double quote character should either be the beginning or end of a comment.<br>
>><br>
>>I suppose it's more complicated than that.<br>
><br>
>It's more complicated. But why don't you put your text into a comment? Actually that's what comments are for in the language.<br>
<br>
</div>Correct, however...<br>
I'm thinking of the case where I have a bunch of snippets in a Workspace, some of which would not work as pasted and therefore cause a syntax error but I still want to leave them as code and maybe later fix the syntax, or use the coloring to see where the syntax error might be occurring in the snippet.<br>
The first syntax error seems to mess syntax highlighting up forever more after the first error i the Workspace. I would like stuff that is actually commented out farther on to to keep showing as comments, even tho there is a syntax error in some code above on the page.<br>
<br>
Or the case where there was that invisible char as first char on the page and the commented section immediately after did not show as a comment color.<br>
It seems to me that the syntax checker could reset at the next double quote after a syntax error since that must be the start of an actual comment because there would never be an actual syntax error inside a quoted section... Yes?<br>
<font color="#888888"><br></font></blockquote></div><div><br></div>What if the syntax error is a missing double quote? The next double quote would indicate the end of the real comment thus causing more syntax errors. I think perhaps you should keep broken code or general text in comments so you can keep the rest of the syntax coloring.<br clear="all">
<br>-- <br>Edwin G. Castro<br><br>