runtime(doc): capitalize correctly
* 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:
@ -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
|
||||
@ -1006,7 +1006,7 @@ Another option is using 'makeencoding'.
|
||||
==============================================================================
|
||||
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
|
||||
powerful Vim search patterns. An external grep program can be used when the
|
||||
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
|
||||
|
||||
|
||||
5.1 using Vim's internal grep
|
||||
5.1 Using Vim's internal grep
|
||||
|
||||
*:vim* *:vimgrep* *E682* *E683*
|
||||
:vim[grep][!] /{pattern}/[g][j][f] {file} ...
|
||||
|
||||
Reference in New Issue
Block a user