You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can look into this, but wanted to give you a heads up.
@mtoy-googly-moogly had responded:
What I thought you asked was for me to do the "highlight", which only depends on the token stream, even if the parse failed. I believe this is what is implemented. The "symbols" pass is only run if the parse runs without errors.
Are you saying that the "highlight" recognizer is not running when there are syntax errors, but it once did.
Are you saying the "highlight" recognizer has always been skipped on syntax errors?
Are you saying that I misunderstood you and you expect the "symbols" recognizer to be run, even when the parse returns syntax errors?
The text was updated successfully, but these errors were encountered:
@christopherswenson had written:
@mtoy-googly-moogly It seems like we're no longer highlighting when there's a bad parse again.
I can look into this, but wanted to give you a heads up.
@mtoy-googly-moogly had responded:
What I thought you asked was for me to do the "highlight", which only depends on the token stream, even if the parse failed. I believe this is what is implemented. The "symbols" pass is only run if the parse runs without errors.
Are you saying that the "highlight" recognizer is not running when there are syntax errors, but it once did.
Are you saying the "highlight" recognizer has always been skipped on syntax errors?
Are you saying that I misunderstood you and you expect the "symbols" recognizer to be run, even when the parse returns syntax errors?
The text was updated successfully, but these errors were encountered: