-
Notifications
You must be signed in to change notification settings - Fork 30
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
Numbers in embedded cpp markdown are not highlighted #97
Comments
Does embedded actually use the extension or does it use the default (1.4.5 1.33.0, atom/language-c 1.33.1, 1.7.6 insiders)? Edit: looks from your response that its yes. |
Thankfully it uses the extension. |
Yeah, pull from master I push pushed a large fix that was thanks to replacing all instances of |
The issue with |
Why was |
I believe that |
I am fairly sure that is incorrect. From https://macromates.com/manual/en/language_grammars
From https://www.apeth.com/nonblog/stories/textmatebundle.html
|
oops, yup looks like we should switch to using The C grammar still needs the fix. |
I can switch both to self in an hour or so. |
Here is the vscode-textmate's And for the simple pattern https://gist.github.com/matter123/63ad7294e30926ad254ccfe84bc932e4 |
This is fixed by microsoft/vscode-textmate#88 |
Thanks for looking into this so deeply. Thats a really nice That is also a really good catch with the objective-c dependency, I have no idea how you found that. Looks like we can't fix embedded c until we also change objective-c. Whenever I get a chance to work on this again I might go ahead and create an objective c repo just for the embedding fix. |
vscode-textmate/#88 was merged in today. I'll close this as soon as insiders has the new version, and I confirm its fixed. |
Great, that means we can probably move forward with the almost-perfect preprocessor conditional pattern for #31 |
With
The numbers have correct highlighting. |
This is inside of a markdown document.
There is this intersting issue where numbers are not tagged.
Adding the pattern^ above the full number pattern actually fixes the issue (but it obviously breaks the complex number matching). My guess is that the number pattern is timing out, which I find surprising. The pattern is really long, but it should be able to match a two digit number in a very short amount of time. I'm also not exactly sure why it behaves different when it is embedded.
The text was updated successfully, but these errors were encountered: