Mercurial > vim

comparison runtime/colors/README.txt @ 13039:e265f0b93bb4 v8.0.1395

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.0.1395: it is not easy to see if a colorscheme is well written commit https://github.com/vim/vim/commit/200d0e36bc5384beb9dc76ac75806ac0aecf84ac Author: Bram Moolenaar <Bram@vim.org> Date: Sat Dec 16 18:53:35 2017 +0100 patch 8.0.1395: it is not easy to see if a colorscheme is well written Problem: It is not easy to see if a colorscheme is well written. Solution: Add a script that checks for common mistakes. (Christian Brabandt)
author Christian Brabandt <cb@256bit.org>
date Sat, 16 Dec 2017 19:00:06 +0100
parents 169a62d5bcb9
children 0d23a49da746
comparison
equal deleted inserted replaced
13038:eb69636598a1 13039:e265f0b93bb4
62 Search for "highlight_init". 62 Search for "highlight_init".
63 63
64 If you think you have a color scheme that is good enough to be used by others, 64 If you think you have a color scheme that is good enough to be used by others,
65 please check the following items: 65 please check the following items:
66 66
67 - Source the check_colors.vim script to check for common mistakes.
67 - Does it work in a color terminal as well as in the GUI? 68 - Does it work in a color terminal as well as in the GUI?
68 - Is "g:colors_name" set to a meaningful value? In case of doubt you can do 69 - Is "g:colors_name" set to a meaningful value? In case of doubt you can do
69 it this way: 70 it this way:
70 let g:colors_name = expand('<sfile>:t:r') 71 let g:colors_name = expand('<sfile>:t:r')
71 - Is 'background' either used or appropriately set to "light" or "dark"? 72 - Is 'background' either used or appropriately set to "light" or "dark"?