You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In VSCode, the default setting highlights a file name in yellow if there's a warning, and in red if there's an error, as demonstrated in the image below:
It would be quite handy if, for instance, using // TODO: would turn the file name yellow as well, indicating there's a TODO item without the need to open the file. Similarly, using // FIXME: could turn the file red. Alternatively, we could use different colors, such as blue and orange, to distinguish these markers from actual compile warnings and errors. I believe the colors for actual warnings and errors should take precedence over those for TODO / FIXME markers.
This feature could be enabled by default, with the option to disable it in the settings.
The text was updated successfully, but these errors were encountered:
In VSCode, the default setting highlights a file name in yellow if there's a warning, and in red if there's an error, as demonstrated in the image below:
It would be quite handy if, for instance, using // TODO: would turn the file name yellow as well, indicating there's a TODO item without the need to open the file. Similarly, using // FIXME: could turn the file red. Alternatively, we could use different colors, such as blue and orange, to distinguish these markers from actual compile warnings and errors. I believe the colors for actual warnings and errors should take precedence over those for TODO / FIXME markers.
This feature could be enabled by default, with the option to disable it in the settings.
The text was updated successfully, but these errors were encountered: