-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#2686 #8
Comments
i'll run tests for your commit. |
Thanks! @IshaanVerma1130 |
|
I think |
It's '\n' in the input code. But it's reading it separately as '\' and 'n'. I believe it should be reading them as newlines as indicated by the comments in the code. |
Ah I see, missed that part, I'll fix it |
Hello, I made a simple fix to the issue. This is the new output for a test file: Also, I think it is better to mark This is my result after the fix: I believe this fixed a HACK in the lexer as well. |
I believe it should still be marked as TEXT.WHITESPACE. Looking at the other Lexers and what they do. Also according to this message, the issue says that some characters should be read as escape character: Take a look at this: https://www.learnxinyminutes.com/docs/tcl/ |
I think asking them would be nice, would you mind adding a comment to the issue asking for clarification? |
The author still hasn't replied. T_T |
I found another issue in the repo, which is #2686. It is a relatively new issue.
The text was updated successfully, but these errors were encountered: