-
Notifications
You must be signed in to change notification settings - Fork 519
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
Main text considered as string by VS Code? [Single " is causing issues] #603
Comments
Can you please give an example on how it changed? I am personally using the |
@James-Yu Thanks for reply! Actually, I happen to use |
I suppose so. Do you mind posting a screenshot on the text which you think the highlighter was doing wrong? |
@James-Yu I just edited the main post above. |
@jlelong do you mind have a brief check on this issue? I'm scratching my head to understand the |
After some trial and error, I have just found where the issue comes from! I have the following macro in the preamble:
The above piece of macro is obtained from: https://tex.stackexchange.com/questions/187162/vertical-bar-for-absolute-value-and-conditional-expectation After deleting the |
Hmm, I'll do some debug on this. |
It seems that 122b706 is the problem. I'm working on a solution. |
This is related to #593. I plan to make a PR on all this by the end of the day. |
@jlelong Please kindly note that I just pushed a dirty hack which removes |
After updating to version 5.3.2., the main text in a tex file is considered as string by VS Code. As a consequence, the color for the syntax highlighting is changed (as well as the rule for word-based suggestions).
Is that an intentional change to treat the text as string?
Update:
I know that VS Code treat these text as string because after I change the setting for string in
editor.tokenColorCustomizations
, the color of the text is changed.Update2:
It turns out that the problem is caused by a piece of macro in the preamble:
After removing
"
near the end of that piece of macro, the main text will be correctly recognized as before (rather than string).The text was updated successfully, but these errors were encountered: