The highlighter doesn't work
See original GitHub issueHello!
I tried to use this extension to highlight my Go
files on latest VSCode but it didn’t work. I followed the guide and set workbench.colorCustomizations
, there was nothing changed.
I have no idea what’s wrong, any advice?
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Highlighting of text does not work correctly
Highlighting of text does not work correctly. When I attempt to highlight text and hold down the mouse button at where I want...
Read more >Why won't highlight text work? (Edit PDF) - Acrobat Answers
The highlight text tool can only highlight "real" text. If you have a scanned document or a document in which text was converted...
Read more >Highlighter Doesn't Work - Adobe Support Community
Solved: My highlighter tool in Acrobat Pro DC stopped working! Can anyone help me? I press the highlighter icon on top of my...
Read more >Highlighting doesn't work – here's what does - Student News
Highlighting is a popular method of studying. Unfortunately, studies show that highlighting isn't useful at all. In fact, the overall utility is ...
Read more >Highlighting Is Ineffective—Here's How to Change That
Research shows that typical highlighting may hinder learning. Here are three highlighting strategies that actually work.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for your explanation. Since the new version has fixed the bug, I think we can close the issue.
The reason has a long story (=. The main cause is this line in
tree-sitter-web
implementation. Basically, it checks that provided path is absolute, but in a strange way. It assumes that no protocol must be specified. On Windows though absolute paths have formC:/Users/...
, soC
is treated as protocol and everything goes wrong. So for Windows I made workaround removing drive letter and using paths of form/Users/...
when loading parser’s wasm. By default such path points to file on C:\ drive. This fix is so ugly, that I haven’t even pushed it to the repo. So this worked in general, not many people install VSCode on secondary drives. Fortunately, the bug is already fixed in this commit. So today I’ll publish the new version that will work when VSCode is installed on any drive (=. Thank you very much for discovering this issue.