diff options
| -rw-r--r-- | Filelist | 1 | ||||
| -rw-r--r-- | runtime/colors/README.txt | 2 | ||||
| -rw-r--r-- | runtime/colors/tools/check_colors.vim (renamed from runtime/colors/check_colors.vim) | 0 | ||||
| -rw-r--r-- | src/version.c | 2 |
4 files changed, 4 insertions, 1 deletions
@@ -666,6 +666,7 @@ RT_SCRIPTS = \ runtime/autoload/xml/*.vim \ runtime/colors/*.vim \ runtime/colors/README.txt \ + runtime/colors/tools/*.vim \ runtime/compiler/*.vim \ runtime/compiler/README.txt \ runtime/indent/*.vim \ diff --git a/runtime/colors/README.txt b/runtime/colors/README.txt index c5a75678b..a435c2dd1 100644 --- a/runtime/colors/README.txt +++ b/runtime/colors/README.txt @@ -64,7 +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. +- Source the 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: diff --git a/runtime/colors/check_colors.vim b/runtime/colors/tools/check_colors.vim index 0cfe5ec12..0cfe5ec12 100644 --- a/runtime/colors/check_colors.vim +++ b/runtime/colors/tools/check_colors.vim diff --git a/src/version.c b/src/version.c index 912e3be33..2da64a273 100644 --- a/src/version.c +++ b/src/version.c @@ -772,6 +772,8 @@ static char *(features[]) = static int included_patches[] = { /* Add new patch number below this line */ /**/ + 1400, +/**/ 1399, /**/ 1398, |