-
Notifications
You must be signed in to change notification settings - Fork 66
language-todo does not work with tree-sitter #82
Comments
Are you using the new Tree-Sitter Parsers option? |
Ah. Yes, I'm using Tree Sitter Parsers. If I turn it off then highlighting of |
Are there plans to support, tree-sitter grammars? I'd be happy to help with this, since we're trying to achieve the same in the hydrogen package. See atom/atom#18196 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
FYI: Still broken w/ Tree Sitter disabled in Terraform (.tf) files. |
This comment has been minimized.
This comment has been minimized.
I fully expect to be removed for spam, but this is a valid question that deserves to be here and to be answered... Since this is an Atom-sponsored package, we expect it to work properly with Core option defaults. This bug has just hit 1 year old. Can we get an update? Any visibility you can give us on the status of remediation? Is there any workaround besides the one that disables other syntax highlighting to enable this? |
EDIT: Looks like what broke TODO highlighting was I have tree-sitters disabled but still encountering this problem.
Under these conditions, inline comments ( |
Is there any news on whether anyone is working on this or if it's even possibe to fix? This highlighting was a great atom feature, and tree-sitter parsers seem to be quite a lot faster, so a pain to loose. |
I reported this on the language-javascript repo as well, since I think they need to modify that library to fix this for JS files. Based on these docs, language-javascript will need to add an injection point inside of all comment nodes, and then tell the parser to let the language-todo grammar take over, which would require setting an injectionRegex in this repository. I'm not sure if this requires having a tree-sitter parser just for TODOs, or if it will still be compatible with the current textgrammar/regex grammar. |
Any word on an update for this or suggestions for how I can patch it on my machine? language-todo has the potential to be incredibly helpful, but I'd like it to work with Tree Sitter. I'm unfortunately not involved enough to be able to fix it myself. |
Still broken, missing this feature! |
No news in two years...I guess we can't expect a fix soon, can we? |
Probably not. GitHub is too busy purging repositories in response to illegal takedown requests (youtube-dl) to worry about this basic functionality. |
I'm taking a look at fixing this. I wouldn't get your hopes up though. I'm a new contributor and I think this might actually be more complicated than it looks. |
Either way, thank you for taking a look at this @bookofportals, your effort is appreciated! :) |
Whoever figures this out will be a real hero! I have to use the tree-sitter parser for TypeScript syntax to work, but it means I lose my TODOs, NOTEs, and FIXMEs. |
I'm not sure how atom highlights works on a deep level, nor tree-sitter parsers, but I am also having this issue. |
language-todo 0.29.4 |
Thank you for the link. Interestingly, it works in the .less file itself, but not in python-files for me. Any ideas? |
You can press Ctrl-Shift-I to open DevTools, then click arrow-like button at the top left corner, then select a part of code with |
For me, in Ruby, there is no additional elements inside comments at all:
So… probably it's language-specific-plugin issue, probably this work-around not for tree-sitter at all (I doubt). |
Same in Python.
It only works if I disable tree-sitter. |
Prerequisites
Description
Highlighting has stopped working in JavaScript and Python files
Steps to Reproduce
TODO
in a commentExpected behavior:
TODO
is highlighted, is in its own<span>
with classsyntax--storage
Actual behavior:
TODO
is grey/the same colour as the rest of the comment, is in the same<span>
as the rest of the comment without classsyntax--storage
Versions
Atom: 1.29.0
Electron: 2.0.5
Chrome: 61.0.3163.100
Node: 8.9.3
Additional information
Highlighting still works for C#
The text was updated successfully, but these errors were encountered: