Mercurial > vim

comparison runtime/doc/syntax.txt @ 8673:ed7251c3e2d3

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
commit https://github.com/vim/vim/commit/e18c0b39815c5a746887a509c2cd9f11fadaba07 Author: Bram Moolenaar <Bram@vim.org> Date: Sun Mar 20 21:08:34 2016 +0100 Updated runtime files.
author Christian Brabandt <cb@256bit.org>
date Sun, 20 Mar 2016 21:15:06 +0100
parents 88207f4b861a
children 47f17f66da3d
comparison
equal deleted inserted replaced
8672:7d1058fed5fb 8673:ed7251c3e2d3
1 *syntax.txt* For Vim version 7.4. Last change: 2016 Feb 25 1 *syntax.txt* For Vim version 7.4. Last change: 2016 Mar 12
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
4532 feature it will output "unknown". 4532 feature it will output "unknown".
4533 4533
4534 :colo[rscheme] {name} Load color scheme {name}. This searches 'runtimepath' 4534 :colo[rscheme] {name} Load color scheme {name}. This searches 'runtimepath'
4535 for the file "colors/{name}.vim". The first one that 4535 for the file "colors/{name}.vim". The first one that
4536 is found is loaded. 4536 is found is loaded.
4537 To see the name of the currently active color scheme: > 4537 Also searches all plugins in 'packpath', first below
4538 :colo 4538 "start" and then under "opt".
4539 < The name is also stored in the g:colors_name variable. 4539
4540 Doesn't work recursively, thus you can't use 4540 Doesn't work recursively, thus you can't use
4541 ":colorscheme" in a color scheme script. 4541 ":colorscheme" in a color scheme script.
4542 After the color scheme has been loaded the 4542 After the color scheme has been loaded the
4543 |ColorScheme| autocommand event is triggered. 4543 |ColorScheme| autocommand event is triggered.
4544 For info about writing a colorscheme file: > 4544 For info about writing a colorscheme file: >