Editing
Colour comments by intent
Editing · 1 min read
Start a comment with !, ?, or * and it takes a colour. Start one with a second // and it fades, because that is code you commented out.
When you would want it
A warning, an open question, and a line of dead code are three different kinds of writing that all render the same grey. One character tells them apart.
Where to find it
- All Features → Colour comments by intent
- Turn on or off
- Settings
What you get out of it
- Warnings, open questions, and dead code stop rendering as the same grey sentence.
- Intent travels with the comment itself - no plugin, no config file per project.
How to use it, step by step
- Turn it on in Editing settings - it is off by default.
- Start a line comment with ! for a warning, ? for a question, or * for a highlight; each takes its own colour.
- A comment starting with // extra slashes fades instead, marking code you commented out.
- Block comments are deliberately untouched: their leading asterisk is a convention, not an intent.
Why this beats the usual way
TODO-highlighters catch tags but lump every other comment together. Toning by the first character makes the whole comment stream readable at a skim, including the 'this is commented-out code' case everyone gets wrong.
Find it in Universal Search
Colour comments by intent · Editing