-
Notifications
You must be signed in to change notification settings - Fork 293
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
Active linenumber colour highlighting property - and vim relative numbering highlights #487
Comments
will fix it soon~ |
Thanks. Not a deal-breaker at all, but it's a very useful addition for that mode/workflow. Much appreciated. |
Maybe |
@r44083 i think #abb2bf is better, but user still can use custom color |
Definitely better to allow custom colour. |
just release a new version~ |
@irisida did you set editor.renderLineHighlight to "all" |
I hadn't no. I have now and hey presto! It's even more fabulous than I'd hoped. Thank you! (starred the repo. You people are all kinds of awesome) |
Describe what you want
I would like to have the ability to use/set the
"editorLineNumber.activeForeground": "#fffff"
property. This would be exceptionally useful for vim mode users with relative line numbering which is a key part of the workflow for many.The expected outcome would be that the current line and highlighting of the theme allows for default or user-selected highlight colour that differentiates from the other lines of the file and their respective line numbering.
Additional context
attached a screenshot showing the relative numbering setup and hopefully, it demonstrates why the highlighting would be useful.
An even further incredible addition/extension to above would be to be able to highlight the tenth line either side with a different colour too. Or all multiples of ten thereafter, as an additional visual/cognitive easing. But it's probably most useful to people with a relative line numbering setup so may not be as mainstream as the first part of the request for the current line number highlight.

The text was updated successfully, but these errors were encountered: