-
Notifications
You must be signed in to change notification settings - Fork 421
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
TODO/FIXME highlighting #523
Comments
Personally believe this should be left to a Plugin |
Instead of a plugin, is there a way to allow configuring certain matches being colored differently? I browse logs in editor, and it helps a lot to highlight ERROR and similar lines in red, WARN and similar in yellow, etc. Instead, Sublime allows you to add a few directives how to color certain files, example I use for the log files:
|
It would be cool if this would also highlight things like Rust's |
Would be nice to have a plugin like VSCode's TODO Highlight v2, which is extremely configurable. |
FYI: I put the comment on zed-industries/zed#6013, but dos not seem this feature is implemented in latest releases. |
This is not merged yet, correct? |
In the zed source code, see zed-industries/zed#9082 |
Hello, Today I have downloaded on linux, I was a VS code user and i am trying to find better alternative, in vs code there was one extension which i used a lot called TODO tree, where my all todo, fixme, bug are shown in single place, is there anything similer to that here? |
Just checking in to see if there's been any progress or updates on extension capabilities that might support this feature? This is one of the few remaining features impacting my decision to fully adopt Zed, and I'm really eager to see it implemented. Any insights or timelines from the extension team would be greatly appreciated by those of us who have been patiently waiting for this issue to be resolved. If there are ways we could contribute or assist in bringing this feature to fruition, please let us know. |
This would be awesome. Switched to Zed from NVim and would love this feature / extension |
this would be a nice feature to have |
would like this as well |
I completely understand the initial notion that this seems to be better implemented as a plugin, BUT I do think a integrated comment tag system (with configurable and sensible defaults) would really set zed apart (e.g., using TODO tree in VS Code is supper convenient). Think of it as a nice addition of the 'Standard Library' of zed. |
Well.. one thing should be mentioned I do not think it is exactly possible to get it as a plugin. I did try to dab at it, but no success. TBH, whatever I was trying to do was related to line wrapping, which I think would have the implementation logic somewhat similar. I was able to create a dummy extension template and install it, but any further changes always took me to the editor level modification, which I need to admit was a notch beyond my comprehension. To be more precise, I do not think plugins level let you access editor level crate for mods 🤔 Checking further the documentation on extensions, I think they are limited to: themes, languages, slash commands (https://zed.dev/docs/extensions/developing-extensions). Maybe I am misinterpreting something, but AFAIK the modification will need to happen in the base code. P.S.: If there is a way to do it at the plugin level, I would be happy to get some guidance from the devs and do it. BTW: I did try to use zed-chat, seeking guidance, but I did not get any answers... :( |
This should absolutely be in the core zed product. Sorry, but saying this is best as a plugin is not understanding the product you're even building. I don't want to have to install dozens of dependencies to get basic programming features I use every day. |
I absolutely agree. at this point it makes more sense to just use neovim if you want customization |
You're forgetting the fact that extensions can be shipped with the editor by default. |
Check for existing issues
I think it's a common and useful feature, since the mainstream editors (IDEA, VS Code) all support it.
If applicable, add mockups / screenshots to help present your vision of the feature
The text was updated successfully, but these errors were encountered: