Mercurial > vim
diff runtime/doc/map.txt @ 29290:dc4de65a7fb7
Update runtime files
Commit: https://github.com/vim/vim/commit/8a3b805c6c9cae341d560df9c3567ebbe42a7404
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Jun 26 12:21:15 2022 +0100
Update runtime files
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Sun, 26 Jun 2022 13:30:04 +0200 |
| parents | 0eef32b4ebbc |
| children | f8116058ca76 |
line wrap: on
line diff
--- a/runtime/doc/map.txt +++ b/runtime/doc/map.txt @@ -177,7 +177,7 @@ Because it tries to unmap "@@ ", includi 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 n 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 @@ 1.2 SPECIAL ARGUMENTS *:map-argument "<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>