extensions
extensions copied to clipboard
TODO/FIXME highlighting
Check for existing issues
- [X] Completed
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
![image](https://user-images.githubusercontent.com/40336192/211147835-726fb45f-310d-4436-bd6b-39931d99ef4b.png)
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.
VSCode provides a Logfile
color scheme, but Sublime does not.
Instead, Sublime allows you to add a few directives how to color certain files, example I use for the log files:
❯ cat sublime/Logfile.tmLanguage
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>fileTypes</key>
<array>
<string>log</string>
</array>
<key>name</key>
<string>Logfile</string>
<key>patterns</key>
<array>
<dict>
<key>match</key>
<string>^.*(ERROR|Error|error).*$</string>
<key>name</key>
<string>entity.name.tag.log</string>
</dict>
<dict>
<key>match</key>
<string>^.*(WARN|Warn|warn).*$</string>
<key>name</key>
<string>variable.parameter.log</string>
</dict>
<dict>
<key>match</key>
<string>^.*(DEBUG|Debug|debug).*$</string>
<key>name</key>
<string>constant.numeric.log</string>
</dict>
<dict>
<key>match</key>
<string>^.*(INFO|Info|info).*$</string>
<key>name</key>
<string>comment.log</string>
</dict>
</array>
<key>scopeName</key>
<string>source.log</string>
<key>uuid</key>
<string>8728e0fe-14c6-4374-acde-da1857d0a378</string>
</dict>
</plist>
It would be cool if this would also highlight things like Rust's todo!
macro.
Would be nice to have a plugin like VSCode's TODO Highlight v2, which is extremely configurable.
FYI: I put the comment on https://github.com/zed-industries/zed/issues/6013, but dos not seem this feature is implemented in latest releases.
Highlighting comments as warnings and important notes might also be useful.
My experiment, it worked:
This is not merged yet, correct?
My experiment, it worked:
![]()
Curious - did you directly bake this into Zed, or is this an extension?
My experiment, it worked:
Curious - did you directly bake this into Zed, or is this an extension?
In the zed source code, see zed-industries/zed#9082