Mercurial > vim

diff 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
line wrap: on
line diff
--- a/runtime/colors/README.txt
+++ b/runtime/colors/README.txt
@@ -64,6 +64,7 @@ Search for "highlight_init".
 If you think you have a color scheme that is good enough to be used by others,
 please check the following items:
 
+- Source the check_colors.vim script to check for common mistakes.
 - Does it work in a color terminal as well as in the GUI?
 - Is "g:colors_name" set to a meaningful value?  In case of doubt you can do
   it this way: