github/vim-galore
1
0
Fork 0
mirror of https://github.com/mhinz/vim-galore.git synced 2025-02-23 17:49:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

Tips: make "cosmetic changes for colorschemes" clearer

Browse Source 
The wording should be a bit clearer now. Also use one of the standard
colorschemes shipped with Vim.

Closes #128
This commit is contained in:
Marco Hinz 2018-04-13 13:53:45 +02:00
parent 32d6eb0af1
commit a605d459e7
No known key found for this signature in database
GPG Key ID: 1C980A1B657B4A4F
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -2179,19 +2179,21 @@ set complete-=t " disable searching tags
## Cosmetic changes to colorschemes ## Cosmetic changes to colorschemes
Always use a dark gray statusline, no matter what colorscheme is chosen: Always use a dark gray statusline, no matter which colorscheme is chosen:
```vim ```vim
autocmd ColorScheme * highlight StatusLine ctermbg=darkgray cterm=NONE guibg=darkgray gui=NONE autocmd ColorScheme * highlight StatusLine ctermbg=darkgray cterm=NONE guibg=darkgray gui=NONE
``` ```
The same, but only for the "lucius" colorscheme (check `:echo This triggers every time you use `:colorscheme ...`. If you want it to trigger only for
color_name` which should be set by all valid colorschemes): a certain colorscheme:
```vim ```vim
autocmd ColorScheme lucius highlight StatusLine ctermbg=darkgray cterm=NONE guibg=darkgray gui=NONE autocmd ColorScheme desert highlight StatusLine ctermbg=darkgray cterm=NONE guibg=darkgray gui=NONE
``` ```
This triggers only for `:colorscheme desert`.
# Commands # Commands
Useful commands that are good to know. Use `:h :<command name>` to learn more Useful commands that are good to know. Use `:h :<command name>` to learn more