1
- *map.txt* For Vim version 8.2. Last change: 2022 Jun 02
1
+ *map.txt* For Vim version 8.2. Last change: 2022 Jun 18
2
2
3
3
4
4
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -177,16 +177,16 @@ Because it tries to unmap "@@ ", including the white space before the command
177
177
separator "|". Other examples with trailing white space: >
178
178
unmap @@
179
179
unmap @@ # Vim9 script comment
180
- unmap @@ " legacy comment
180
+ unmap @@ " legacy script comment
181
181
182
182
An error will be issued, which is very hard to identify, because the ending
183
183
whitespace character in `unmap @@ ` is not visible.
184
184
185
185
A generic solution is to put the command separator "|" right after the mapped
186
186
keys. After that white space and a comment may follow: >
187
187
188
- unmap @@| # Vim9 scriptcomment
189
- unmap @@| " legacy scriptcomment
188
+ unmap @@| # Vim9 script comment
189
+ unmap @@| " legacy script comment
190
190
191
191
192
192
1.2 SPECIAL ARGUMENTS *:map-arguments*
@@ -195,7 +195,8 @@ keys. After that white space and a comment may follow: >
195
195
"<unique> " can be used in any order. They must appear right after the
196
196
command, before any other arguments.
197
197
198
- *:map-local* *:map-<buffer>* *:map-buffer* *E224* *E225*
198
+ *:map-local* *:map-<buffer>* *:map-buffer*
199
+ *E224* *E225*
199
200
If the first argument to one of these commands is "<buffer> " the mapping will
200
201
be effective in the current buffer only. Example: >
201
202
:map <buffer> ,w /[.,;]<CR>
@@ -394,8 +395,6 @@ Note:
394
395
mapping is recursive.
395
396
- In Visual mode you can use `line (' v' )` and `col (' v' )` to get one end of the
396
397
Visual area, the cursor is at the other end.
397
- - In Select mode, | :map | and | :vmap | command mappings are executed in
398
- Visual mode. Use | :smap | to handle Select mode differently.
399
398
400
399
*E1255* *E1136*
401
400
<Cmd> and <ScriptCmd> commands must terminate, that is, they must be followed
0 commit comments