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

Update runtime files

Browse Source
This commit is contained in:
Bram Moolenaar
2022-06-26 12:21:15 +01:00
parent 0fbc9260a7
commit 8a3b805c6c
30 changed files with 689 additions and 697 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
runtime/doc/map.txt
View File

@ -177,7 +177,7 @@ Because it tries to unmap "@@ ", including the white space before the command
separator "|". Other examples with trailing white space: >
unmap @@
unmap @@ # Vim9 script comment
unmap @@ " legacy comment
unmap @@ " legacy script comment
An error will be issued, which is very hard to identify, because the ending
whitespace character in `unmap @@ ` is not visible.
@ -185,8 +185,8 @@ whitespace character in `unmap @@ ` is not visible.
A generic solution is to put the command separator "|" right after the mapped
keys. After that white space and a comment may follow: >
unmap @@| # Vim9 scriptcomment
unmap @@| " legacy scriptcomment
unmap @@| # Vim9 script comment
unmap @@| " legacy script comment
1.2 SPECIAL ARGUMENTS *:map-arguments*
@ -195,7 +195,8 @@ keys. After that white space and a comment may follow: >
"<unique>" can be used in any order. They must appear right after the
command, before any other arguments.
*:map-local* *:map-<buffer>* *:map-buffer* *E224* *E225*
*:map-local* *:map-<buffer>* *:map-buffer*
*E224* *E225*
If the first argument to one of these commands is "<buffer>" the mapping will
be effective in the current buffer only. Example: >
:map <buffer> ,w /[.,;]<CR>