Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Color Issues
See original GitHub issueI’m not sure how the colors of theme’s are being applied but lots of themes still look worse with the tree sitter, at least for C++ 😕I’d recommend upgrading the C++ TextMate grammar to pull from VS Code’s upstream source but even after that there are some bugs that need to be worked out.
I think this issue will be fixed when the TreeSitter only adds colors, and the added colors correspond to the theme’s colors for those things.
Material Theme:
With the tree sitter:
Without the tree sitter and with the Better C++ Syntax extension (the upstream for the C++ syntax):
XD Theme
Using a theme that is more fitted to C++ make the difference more extreme:
With the tree sitter:
Without tree-sitter, and with Better C++ Syntax
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sounds good!
There is a large challenge around the naming though, longer names are not really sufficient. There is a TextMate naming convention that is used as a standard to get compatibility across languages. On the C++ TextMate repo, we’ve spent a lot of time with people from VS Code coordinating changes to the scopes, how they should be named, and then talking to theme makers when they change. Whenever the TextMate conventions don’t cover something, we search all of the other TextMate grammars in order to find the most similar naming among all languages.
It’s a non trivial task, there are 600 scopes in C++ and more are going to be added throughout the summer. Many of them are generated programmatically. That’s why I recommend starting with an existing C++ grammar and then only removing the parts that the Tree-Sitter replaces.
Ok, I think I understand: right now I have all the keywords in two categories, keyword.control and keyword. Instead I should use the longer, more specific scopes like keyword.other.namespace or whatever it is, so that existing c++ color themes can pick them up and color them differently.
We’ll also need to put back a bunch of punctuation scopes for brackets and things, and it looks like entity.name.type is different than the scope c++ was using before.