diff options
| author | Bram Moolenaar <Bram@vim.org> | 2022-06-26 12:21:15 +0100 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2022-06-26 12:21:15 +0100 |
| commit | 8a3b805c6c9cae341d560df9c3567ebbe42a7404 (patch) | |
| tree | e4698c444eb52cbb7aff2138a8491debceda4c5a /runtime/doc/map.txt | |
| parent | 0fbc9260a75dfc4d86f20e7c0eb76878f513a212 (diff) | |
Update runtime files
Diffstat (limited to 'runtime/doc/map.txt')
| -rw-r--r-- | runtime/doc/map.txt | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt index 91df903a39..91261050d6 100644 --- a/runtime/doc/map.txt +++ b/runtime/doc/map.txt @@ -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> |