diff options
Diffstat (limited to 'runtime/colors/README.txt')
-rw-r--r-- | runtime/colors/README.txt | 33 |
1 files changed, 20 insertions, 13 deletions
diff --git a/runtime/colors/README.txt b/runtime/colors/README.txt index b238451d86..e4af1b9a9c 100644 --- a/runtime/colors/README.txt +++ b/runtime/colors/README.txt @@ -1,14 +1,18 @@ README.txt for color scheme files -These files are used for the ":colorscheme" command. They appear in the +These files are used for the `:colorscheme` command. They appear in the "Edit/Color Scheme" menu in the GUI. +The colorschemes were updated for the Vim 9 release. If you don't like the +changes you can find the old ones here: +https://github.com/vim/colorschemes/tree/master/legacy_colors + Hints for writing a color scheme file: There are two basic ways to define a color scheme: -1. Define a new Normal color and set the 'background' option accordingly. +1. Define a new Normal color and set the 'background' option accordingly. > set background={light or dark} highlight clear @@ -16,7 +20,7 @@ There are two basic ways to define a color scheme: ... 2. Use the default Normal color and automatically adjust to the value of - 'background'. + 'background'. > highlight clear Normal set background& @@ -29,17 +33,17 @@ There are two basic ways to define a color scheme: ... endif -You can use ":highlight clear" to reset everything to the defaults, and then +You can use `:highlight clear` to reset everything to the defaults, and then change the groups that you want differently. This will also work for groups that are added in later versions of Vim. -Note that ":highlight clear" uses the value of 'background', thus set it +Note that `:highlight clear` uses the value of 'background', thus set it before this command. Some attributes (e.g., bold) might be set in the defaults that you want removed in your color scheme. Use something like "gui=NONE" to remove the attributes. In case you want to set 'background' depending on the colorscheme selected, -this autocmd might be useful: +this autocmd might be useful: > autocmd SourcePre */colors/blue_sky.vim set background=dark @@ -49,7 +53,7 @@ In case you want to tweak a colorscheme after it was loaded, check out the ColorScheme autocommand event. To clean up just before loading another colorscheme, use the ColorSchemePre -autocommand event. For example: +autocommand event. For example: > let g:term_ansi_colors = ... augroup MyColorscheme @@ -59,20 +63,20 @@ autocommand event. For example: augroup END To customize a colorscheme use another name, e.g. "~/.vim/colors/mine.vim", -and use ":runtime" to load the original colorscheme: +and use ":runtime" to load the original colorscheme: > " load the "evening" colorscheme runtime colors/evening.vim " change the color of statements hi Statement ctermfg=Blue guifg=Blue -To see which highlight group is used where, see ":help highlight-groups" and -":help group-name". +To see which highlight group is used where, see `:help highlight-groups` and +`:help group-name` . You can use ":highlight" to find out the current colors. Exception: the ctermfg and ctermbg values are numbers, which are only valid for the current terminal. Use the color names instead for better portability. See -":help cterm-colors". +`:help cterm-colors` . The default color settings can be found in the source file src/syntax.c. Search for "highlight_init". @@ -86,7 +90,7 @@ please check the following items: - Does it work in a color terminal as well as in the GUI? Is it consistent? - Is "g:colors_name" set to a meaningful value? In case of doubt you can do - it this way: + it this way: > let g:colors_name = expand('<sfile>:t:r') @@ -121,7 +125,7 @@ please check the following items: - Try to keep your color scheme simple by avoiding unnecessary logic and refraining from adding options. The best color scheme is one that only - requires: + requires: > colorscheme foobar @@ -136,3 +140,6 @@ that: - it was made with colortemplate, and join us at vim/colorschemes: (https://github.com/vim/colorschemes). + + +vim: set ft=help : |