adam/vim
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

runtime(doc): capitalize correctly

Browse Source 
* do not capitalize after a double colon when introducing a list
* Capitalize a header line

closes: #15433

Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
Christian Brabandt
2024-08-05 17:36:09 +02:00
parent f5f69e8663
commit 217d3c17c6
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
runtime/doc/quickfix.txt
View File

@ -1,4 +1,4 @@
*quickfix.txt* For Vim version 9.1. Last change: 2024 Jul 17 *quickfix.txt* For Vim version 9.1. Last change: 2024 Aug 05
VIM REFERENCE MANUAL by Bram Moolenaar VIM REFERENCE MANUAL by Bram Moolenaar
@ -1006,7 +1006,7 @@ Another option is using 'makeencoding'.
============================================================================== ==============================================================================
5. Using :vimgrep and :grep *grep* *lid* 5. Using :vimgrep and :grep *grep* *lid*
Vim has two ways to find matches for a pattern: Internal and external. The Vim has two ways to find matches for a pattern: internal and external. The
advantage of the internal grep is that it works on all systems and uses the advantage of the internal grep is that it works on all systems and uses the
powerful Vim search patterns. An external grep program can be used when the powerful Vim search patterns. An external grep program can be used when the
Vim grep does not do what you want. Vim grep does not do what you want.
@ -1035,7 +1035,7 @@ commands can be combined to create a NewGrep command: >
command! -nargs=+ NewGrep execute 'silent grep! <args>' | copen 42 command! -nargs=+ NewGrep execute 'silent grep! <args>' | copen 42
5.1 using Vim's internal grep 5.1 Using Vim's internal grep
*:vim* *:vimgrep* *E682* *E683* *:vim* *:vimgrep* *E682* *E683*
:vim[grep][!] /{pattern}/[g][j][f] {file} ... :vim[grep][!] /{pattern}/[g][j][f] {file} ...