-
Notifications
You must be signed in to change notification settings - Fork 64
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
Vim: style remaining default groups #67
Comments
jan-warchol
added a commit
that referenced
this issue
Mar 6, 2020
Having magenta for identifiers was IMO too overwhelming (e.g. in Python or shell code). OTOH, PreProc somehow agrees with magenta in my mind - perhaps because it works on another "level", and it seems to fit a non-spectral color. Related to #67
jan-warchol
added a commit
that referenced
this issue
Mar 6, 2020
The idea is to make the theme behave better if someone is forced to use it in a virtual terminal (e.g. because X crashed), which is known to have very dark blue. However, I'm not entirely convinced. Related to #67
I might have a go at this and see how I go |
jan-warchol
added a commit
that referenced
this issue
Mar 8, 2020
Having magenta for identifiers was IMO too overwhelming (e.g. in Python or shell code). OTOH, PreProc somehow agrees with magenta in my mind - perhaps because it works on another "level", and it seems to fit a non-spectral color. Related to #67
jan-warchol
added a commit
that referenced
this issue
Mar 8, 2020
The idea is to make the theme behave better if someone is forced to use it in a virtual terminal (e.g. because X crashed), which is known to have very dark blue. However, I'm not entirely convinced. Related to #67
Merged
jan-warchol
added a commit
that referenced
this issue
Mar 22, 2020
Having magenta for identifiers was IMO too overwhelming (e.g. in Python or shell code). OTOH, PreProc somehow agrees with magenta in my mind - perhaps because it works on another "level", and it seems to fit a non-spectral color. Related to #67
jan-warchol
added a commit
that referenced
this issue
Mar 22, 2020
The idea is to make the theme behave better if someone is forced to use it in a virtual terminal (e.g. because X crashed), which is known to have very dark blue. However, I'm not entirely convinced. Related to #67
jan-warchol
added a commit
that referenced
this issue
Mar 24, 2020
jan-warchol
added a commit
that referenced
this issue
Apr 1, 2020
The idea is to make the theme behave better if someone is forced to use it in a virtual terminal (e.g. because X crashed), which is known to have very dark blue. Related to #67
clach04
pushed a commit
to clach04/selenized
that referenced
this issue
Dec 14, 2024
clach04
pushed a commit
to clach04/selenized
that referenced
this issue
Dec 14, 2024
The idea is to make the theme behave better if someone is forced to use it in a virtual terminal (e.g. because X crashed), which is known to have very dark blue. Related to jan-warchol#67
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#59 implemented minimal styling necessary to use selenized with Vim, but some highlight groups remained unstyled (they are listed at the end of the template file).
Remember to test the results in terminal&GUI, vim&neovim.
The text was updated successfully, but these errors were encountered: