summaryrefslogtreecommitdiffstats
path: root/runtime/colors
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2018-05-06 17:57:30 +0200
committerBram Moolenaar <Bram@vim.org>2018-05-06 17:57:30 +0200
commit85eee130f44a2201d88ca2aeff0af3b11dd75fa9 (patch)
tree1748e216e4f90786b1a0789a054568976da40c42 /runtime/colors
parent7ce551f317a0bb92f8c0521e96325301e2d220ca (diff)
Update runtime files.
Diffstat (limited to 'runtime/colors')
-rw-r--r--runtime/colors/README.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/runtime/colors/README.txt b/runtime/colors/README.txt
index 4511748daf..057bbec51f 100644
--- a/runtime/colors/README.txt
+++ b/runtime/colors/README.txt
@@ -73,7 +73,8 @@ 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 tools/check_colors.vim script to check for common mistakes.
+- Source the $VIMRUNTIME/colors/tools/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: