Mercurial > vim
annotate runtime/doc/map.txt @ 29377:48b086982c01 v9.0.0031
patch 9.0.0031: <cmod> of user command does not have correct verbose value
Commit: https://github.com/vim/vim/commit/9359e8a6d99fe2abfcbb9603339f1740d8870cc6
Author: zeertzjq <zeertzjq@outlook.com>
Date: Sun Jul 3 13:16:09 2022 +0100
patch 9.0.0031: <cmod> of user command does not have correct verbose value
Problem: <cmod> of user command does not have correct verbose value.
Solution: Use the value from the command modifier. (closes https://github.com/vim/vim/issues/10651)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Sun, 03 Jul 2022 14:30:06 +0200 |
| parents | f8116058ca76 |
| children | 03e3b0034e31 |
| rev | line source |
|---|---|
| 29314 | 1 *map.txt* For Vim version 9.0. Last change: 2022 Jun 18 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 Key mapping, abbreviations and user-defined commands. | |
| 8 | |
| 27036 | 9 This subject is introduced in sections |05.4|, |24.7| and |40.1| of the user |
| 7 | 10 manual. |
| 11 | |
| 12 1. Key mapping |key-mapping| | |
| 592 | 13 1.1 MAP COMMANDS |:map-commands| |
| 14 1.2 Special arguments |:map-arguments| | |
| 15 1.3 Mapping and modes |:map-modes| | |
| 16 1.4 Listing mappings |map-listing| | |
| 17 1.5 Mapping special keys |:map-special-keys| | |
| 18 1.6 Special characters |:map-special-chars| | |
| 19 1.7 What keys to map |map-which-keys| | |
| 20 1.8 Examples |map-examples| | |
| 21 1.9 Using mappings |map-typing| | |
| 22 1.10 Mapping alt-keys |:map-alt-keys| | |
|
18400
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
23 1.11 Mapping in modifyOtherKeys mode |modifyOtherKeys| |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
24 1.12 Mapping an operator |:map-operator| |
| 7 | 25 2. Abbreviations |abbreviations| |
| 26 3. Local mappings and functions |script-local| | |
| 27 4. User-defined commands |user-commands| | |
| 28 | |
| 29 ============================================================================== | |
| 30 1. Key mapping *key-mapping* *mapping* *macro* | |
| 31 | |
| 32 Key mapping is used to change the meaning of typed keys. The most common use | |
| 12559 | 33 is to define a sequence of commands for a function key. Example: > |
| 7 | 34 |
| 35 :map <F2> a<C-R>=strftime("%c")<CR><Esc> | |
| 36 | |
| 236 | 37 This appends the current date and time after the cursor (in <> notation |<>|). |
| 7 | 38 |
| 592 | 39 |
| 40 1.1 MAP COMMANDS *:map-commands* | |
| 41 | |
| 7 | 42 There are commands to enter new mappings, remove mappings and list mappings. |
| 43 See |map-overview| for the various forms of "map" and their relationships with | |
| 44 modes. | |
| 45 | |
| 46 {lhs} means left-hand-side *{lhs}* | |
| 47 {rhs} means right-hand-side *{rhs}* | |
| 48 | |
| 663 | 49 :map {lhs} {rhs} |mapmode-nvo| *:map* |
| 50 :nm[ap] {lhs} {rhs} |mapmode-n| *:nm* *:nmap* | |
| 51 :vm[ap] {lhs} {rhs} |mapmode-v| *:vm* *:vmap* | |
| 788 | 52 :xm[ap] {lhs} {rhs} |mapmode-x| *:xm* *:xmap* |
| 4358 | 53 :smap {lhs} {rhs} |mapmode-s| *:smap* |
| 663 | 54 :om[ap] {lhs} {rhs} |mapmode-o| *:om* *:omap* |
| 55 :map! {lhs} {rhs} |mapmode-ic| *:map!* | |
| 56 :im[ap] {lhs} {rhs} |mapmode-i| *:im* *:imap* | |
| 16944 | 57 :lm[ap] {lhs} {rhs} |mapmode-l| *:lm* *:lma* *:lmap* |
| 663 | 58 :cm[ap] {lhs} {rhs} |mapmode-c| *:cm* *:cmap* |
| 12499 | 59 :tma[p] {lhs} {rhs} |mapmode-t| *:tma* *:tmap* |
| 7 | 60 Map the key sequence {lhs} to {rhs} for the modes |
| 61 where the map command applies. The result, including | |
| 62 {rhs}, is then further scanned for mappings. This | |
| 63 allows for nested and recursive use of mappings. | |
| 26148 | 64 Note: Trailing spaces are included in the {rhs}, |
| 65 because space is a valid Normal mode command. | |
| 29066 | 66 See |map-trailing-white|. |
| 7 | 67 |
| 5968 | 68 *:nore* *:norem* |
| 69 :no[remap] {lhs} {rhs} |mapmode-nvo| *:no* *:noremap* *:nor* | |
| 70 :nn[oremap] {lhs} {rhs} |mapmode-n| *:nn* *:nnoremap* | |
| 71 :vn[oremap] {lhs} {rhs} |mapmode-v| *:vn* *:vnoremap* | |
| 72 :xn[oremap] {lhs} {rhs} |mapmode-x| *:xn* *:xnoremap* | |
| 16944 | 73 :snor[emap] {lhs} {rhs} |mapmode-s| *:snor* *:snore* *:snoremap* |
| 5968 | 74 :ono[remap] {lhs} {rhs} |mapmode-o| *:ono* *:onoremap* |
| 75 :no[remap]! {lhs} {rhs} |mapmode-ic| *:no!* *:noremap!* | |
| 16944 | 76 :ino[remap] {lhs} {rhs} |mapmode-i| *:ino* *:inor* *:inoremap* |
| 5968 | 77 :ln[oremap] {lhs} {rhs} |mapmode-l| *:ln* *:lnoremap* |
| 16944 | 78 :cno[remap] {lhs} {rhs} |mapmode-c| *:cno* *:cnor* *:cnoremap* |
|
12457
dfb8254aa735
patch 8.0.1108: cannot specify mappings for the terminal window
Christian Brabandt <cb@256bit.org>
parents:
12419
diff
changeset
|
79 :tno[remap] {lhs} {rhs} |mapmode-t| *:tno* *:tnoremap* |
| 7 | 80 Map the key sequence {lhs} to {rhs} for the modes |
| 81 where the map command applies. Disallow mapping of | |
| 82 {rhs}, to avoid nested and recursive mappings. Often | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
83 used to redefine a command. |
|
27946
5147f3d3ed30
patch 8.2.4498: using <Plug> with "noremap" does not work
Bram Moolenaar <Bram@vim.org>
parents:
27903
diff
changeset
|
84 Note: When <Plug> appears in the {rhs} this part is |
|
5147f3d3ed30
patch 8.2.4498: using <Plug> with "noremap" does not work
Bram Moolenaar <Bram@vim.org>
parents:
27903
diff
changeset
|
85 always applied even if remapping is disallowed. |
| 7 | 86 |
| 87 | |
| 663 | 88 :unm[ap] {lhs} |mapmode-nvo| *:unm* *:unmap* |
| 89 :nun[map] {lhs} |mapmode-n| *:nun* *:nunmap* | |
| 90 :vu[nmap] {lhs} |mapmode-v| *:vu* *:vunmap* | |
| 788 | 91 :xu[nmap] {lhs} |mapmode-x| *:xu* *:xunmap* |
| 92 :sunm[ap] {lhs} |mapmode-s| *:sunm* *:sunmap* | |
| 663 | 93 :ou[nmap] {lhs} |mapmode-o| *:ou* *:ounmap* |
| 94 :unm[ap]! {lhs} |mapmode-ic| *:unm!* *:unmap!* | |
| 95 :iu[nmap] {lhs} |mapmode-i| *:iu* *:iunmap* | |
| 96 :lu[nmap] {lhs} |mapmode-l| *:lu* *:lunmap* | |
| 16944 | 97 :cu[nmap] {lhs} |mapmode-c| *:cu* *:cun* *:cunmap* |
| 12499 | 98 :tunma[p] {lhs} |mapmode-t| *:tunma* *:tunmap* |
| 7 | 99 Remove the mapping of {lhs} for the modes where the |
| 100 map command applies. The mapping may remain defined | |
| 101 for other modes where it applies. | |
| 26219 | 102 It also works when {lhs} matches the {rhs} of a |
| 27036 | 103 mapping. This is for when an abbreviation applied. |
| 29066 | 104 Note: Trailing spaces are included in the {lhs}. |
| 105 See |map-trailing-white|. | |
| 7 | 106 |
| 663 | 107 :mapc[lear] |mapmode-nvo| *:mapc* *:mapclear* |
| 108 :nmapc[lear] |mapmode-n| *:nmapc* *:nmapclear* | |
| 109 :vmapc[lear] |mapmode-v| *:vmapc* *:vmapclear* | |
| 788 | 110 :xmapc[lear] |mapmode-x| *:xmapc* *:xmapclear* |
| 111 :smapc[lear] |mapmode-s| *:smapc* *:smapclear* | |
| 663 | 112 :omapc[lear] |mapmode-o| *:omapc* *:omapclear* |
| 113 :mapc[lear]! |mapmode-ic| *:mapc!* *:mapclear!* | |
| 114 :imapc[lear] |mapmode-i| *:imapc* *:imapclear* | |
| 115 :lmapc[lear] |mapmode-l| *:lmapc* *:lmapclear* | |
| 116 :cmapc[lear] |mapmode-c| *:cmapc* *:cmapclear* | |
|
12457
dfb8254aa735
patch 8.0.1108: cannot specify mappings for the terminal window
Christian Brabandt <cb@256bit.org>
parents:
12419
diff
changeset
|
117 :tmapc[lear] |mapmode-t| *:tmapc* *:tmapclear* |
| 7 | 118 Remove ALL mappings for the modes where the map |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
119 command applies. |
| 2908 | 120 Use the <buffer> argument to remove buffer-local |
| 121 mappings |:map-<buffer>| | |
|
28808
0f0fed554cdc
Update runtime files, translations
Bram Moolenaar <Bram@vim.org>
parents:
28517
diff
changeset
|
122 Warning: This also removes the |mac-standard-mappings| |
|
0f0fed554cdc
Update runtime files, translations
Bram Moolenaar <Bram@vim.org>
parents:
28517
diff
changeset
|
123 and the |dos-standard-mappings|. |
| 7 | 124 |
| 663 | 125 :map |mapmode-nvo| |
| 126 :nm[ap] |mapmode-n| | |
| 127 :vm[ap] |mapmode-v| | |
| 788 | 128 :xm[ap] |mapmode-x| |
| 129 :sm[ap] |mapmode-s| | |
| 663 | 130 :om[ap] |mapmode-o| |
| 131 :map! |mapmode-ic| | |
| 132 :im[ap] |mapmode-i| | |
| 133 :lm[ap] |mapmode-l| | |
| 134 :cm[ap] |mapmode-c| | |
| 12499 | 135 :tma[p] |mapmode-t| |
| 7 | 136 List all key mappings for the modes where the map |
| 137 command applies. Note that ":map" and ":map!" are | |
| 138 used most often, because they include the other modes. | |
| 139 | |
| 663 | 140 :map {lhs} |mapmode-nvo| *:map_l* |
| 141 :nm[ap] {lhs} |mapmode-n| *:nmap_l* | |
| 142 :vm[ap] {lhs} |mapmode-v| *:vmap_l* | |
| 788 | 143 :xm[ap] {lhs} |mapmode-x| *:xmap_l* |
| 144 :sm[ap] {lhs} |mapmode-s| *:smap_l* | |
| 663 | 145 :om[ap] {lhs} |mapmode-o| *:omap_l* |
| 146 :map! {lhs} |mapmode-ic| *:map_l!* | |
| 147 :im[ap] {lhs} |mapmode-i| *:imap_l* | |
| 148 :lm[ap] {lhs} |mapmode-l| *:lmap_l* | |
| 149 :cm[ap] {lhs} |mapmode-c| *:cmap_l* | |
| 12499 | 150 :tma[p] {lhs} |mapmode-t| *:tmap_l* |
| 7 | 151 List the key mappings for the key sequences starting |
| 152 with {lhs} in the modes where the map command applies. | |
| 153 | |
| 154 These commands are used to map a key or key sequence to a string of | |
| 155 characters. You can use this to put command sequences under function keys, | |
| 156 translate one key into another, etc. See |:mkexrc| for how to save and | |
| 157 restore the current mappings. | |
| 158 | |
| 592 | 159 *map-ambiguous* |
| 160 When two mappings start with the same sequence of characters, they are | |
| 161 ambiguous. Example: > | |
| 162 :imap aa foo | |
| 163 :imap aaa bar | |
| 164 When Vim has read "aa", it will need to get another character to be able to | |
| 165 decide if "aa" or "aaa" should be mapped. This means that after typing "aa" | |
| 166 that mapping won't get expanded yet, Vim is waiting for another character. | |
| 167 If you type a space, then "foo" will get inserted, plus the space. If you | |
| 168 type "a", then "bar" will get inserted. | |
| 169 | |
| 29066 | 170 Trailing white space ~ |
| 171 *map-trailing-white* | |
| 172 This unmap command does NOT work: > | |
| 173 :map @@ foo | |
| 174 :unmap @@ | print | |
| 175 | |
| 176 Because it tries to unmap "@@ ", including the white space before the command | |
| 177 separator "|". Other examples with trailing white space: > | |
| 178 unmap @@ | |
| 179 unmap @@ # Vim9 script comment | |
| 29290 | 180 unmap @@ " legacy script comment |
| 29066 | 181 |
| 182 An error will be issued, which is very hard to identify, because the ending | |
| 183 whitespace character in `unmap @@ ` is not visible. | |
| 184 | |
| 185 A generic solution is to put the command separator "|" right after the mapped | |
| 186 keys. After that white space and a comment may follow: > | |
| 187 | |
| 29290 | 188 unmap @@| # Vim9 script comment |
| 189 unmap @@| " legacy script comment | |
| 29066 | 190 |
| 592 | 191 |
| 192 1.2 SPECIAL ARGUMENTS *:map-arguments* | |
| 193 | |
|
5035
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
194 "<buffer>", "<nowait>", "<silent>", "<special>", "<script>", "<expr>" and |
|
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
195 "<unique>" can be used in any order. They must appear right after the |
|
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
196 command, before any other arguments. |
| 721 | 197 |
| 29290 | 198 *:map-local* *:map-<buffer>* *:map-buffer* |
| 199 *E224* *E225* | |
| 1668 | 200 If the first argument to one of these commands is "<buffer>" the mapping will |
| 201 be effective in the current buffer only. Example: > | |
| 7 | 202 :map <buffer> ,w /[.,;]<CR> |
| 203 Then you can map ",w" to something else in another buffer: > | |
| 204 :map <buffer> ,w /[#&!]<CR> | |
|
5035
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
205 The local buffer mappings are used before the global ones. See <nowait> below |
|
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
206 to make a short local mapping not taking effect when a longer global one |
|
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
207 exists. |
| 7 | 208 The "<buffer>" argument can also be used to clear mappings: > |
| 209 :unmap <buffer> ,w | |
| 210 :mapclear <buffer> | |
| 211 Local mappings are also cleared when a buffer is deleted, but not when it is | |
| 212 unloaded. Just like local option values. | |
| 4869 | 213 Also see |map-precedence|. |
| 7 | 214 |
|
5035
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
215 *:map-<nowait>* *:map-nowait* |
|
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
216 When defining a buffer-local mapping for "," there may be a global mapping |
|
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
217 that starts with ",". Then you need to type another character for Vim to know |
|
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
218 whether to use the "," mapping or the longer one. To avoid this add the |
|
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
219 <nowait> argument. Then the mapping will be used when it matches, Vim does |
|
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
220 not wait for more characters to be typed. However, if the characters were |
| 11473 | 221 already typed they are used. |
| 21991 | 222 Note that this works when the <nowait> mapping fully matches and is found |
| 223 before any partial matches. This works when: | |
| 224 - There is only one matching buffer-local mapping, since these are always | |
| 225 found before global mappings. | |
| 22171 | 226 - There is another buffer-local mapping that partly matches, but it is |
| 21991 | 227 defined earlier (last defined mapping is found first). |
|
5035
1cf89d38aa76
updated for version 7.3.1261
Bram Moolenaar <bram@vim.org>
parents:
4869
diff
changeset
|
228 |
| 7 | 229 *:map-<silent>* *:map-silent* |
| 230 To define a mapping which will not be echoed on the command line, add | |
| 231 "<silent>" as the first argument. Example: > | |
| 232 :map <silent> ,h /Header<CR> | |
| 233 The search string will not be echoed when using this mapping. Messages from | |
| 234 the executed command are still given though. To shut them up too, add a | |
| 235 ":silent" in the executed command: > | |
| 236 :map <silent> ,h :exe ":silent normal /Header\r"<CR> | |
| 237 Prompts will still be given, e.g., for inputdialog(). | |
| 238 Using "<silent>" for an abbreviation is possible, but will cause redrawing of | |
| 239 the command line to fail. | |
| 240 | |
| 859 | 241 *:map-<special>* *:map-special* |
| 242 Define a mapping with <> notation for special keys, even though the "<" flag | |
| 243 may appear in 'cpoptions'. This is useful if the side effect of setting | |
| 244 'cpoptions' is not desired. Example: > | |
| 245 :map <special> <F12> /Header<CR> | |
| 246 < | |
| 7 | 247 *:map-<script>* *:map-script* |
| 248 If the first argument to one of these commands is "<script>" and it is used to | |
| 249 define a new mapping or abbreviation, the mapping will only remap characters | |
| 250 in the {rhs} using mappings that were defined local to a script, starting with | |
| 251 "<SID>". This can be used to avoid that mappings from outside a script | |
| 252 interfere (e.g., when CTRL-V is remapped in mswin.vim), but do use other | |
| 253 mappings defined in the script. | |
| 254 Note: ":map <script>" and ":noremap <script>" do the same thing. The | |
| 255 "<script>" overrules the command name. Using ":noremap <script>" is | |
| 256 preferred, because it's clearer that remapping is (mostly) disabled. | |
| 257 | |
| 26591 | 258 *:map-<unique>* *:map-unique* *E226* *E227* |
| 7 | 259 If the first argument to one of these commands is "<unique>" and it is used to |
| 260 define a new mapping or abbreviation, the command will fail if the mapping or | |
| 261 abbreviation already exists. Example: > | |
| 262 :map <unique> ,w /[#&!]<CR> | |
| 263 When defining a local mapping, there will also be a check if a global map | |
| 264 already exists which is equal. | |
| 265 Example of what will fail: > | |
| 266 :map ,w /[#&!]<CR> | |
| 267 :map <buffer> <unique> ,w /[.,;]<CR> | |
| 626 | 268 If you want to map a key and then have it do what it was originally mapped to, |
| 269 have a look at |maparg()|. | |
| 7 | 270 |
| 721 | 271 *:map-<expr>* *:map-expression* |
| 272 If the first argument to one of these commands is "<expr>" and it is used to | |
| 273 define a new mapping or abbreviation, the argument is an expression. The | |
| 274 expression is evaluated to obtain the {rhs} that is used. Example: > | |
| 24569 | 275 :inoremap <expr> . <SID>InsertDot() |
| 276 The result of the s:InsertDot() function will be inserted. It could check the | |
| 721 | 277 text before the cursor and start omni completion when some condition is met. |
| 24569 | 278 Using a script-local function is preferred, to avoid polluting the global |
| 279 namespace. Use <SID> in the RHS so that the script that the mapping was | |
| 280 defined in can be found. | |
| 721 | 281 |
| 1969 | 282 For abbreviations |v:char| is set to the character that was typed to trigger |
| 283 the abbreviation. You can use this to decide how to expand the {lhs}. You | |
| 3082 | 284 should not either insert or change the v:char. |
| 1969 | 285 |
| 22565 | 286 In case you want the mapping to not do anything, you can have the expression |
| 287 evaluate to an empty string. If something changed that requires Vim to | |
| 288 go through the main loop (e.g. to update the display), return "\<Ignore>". | |
| 289 This is similar to "nothing" but makes Vim return from the loop that waits for | |
| 290 input. Example: > | |
| 291 func s:OpenPopup() | |
| 292 call popup_create(... arguments ...) | |
| 293 return "\<Ignore>" | |
| 294 endfunc | |
| 24569 | 295 nnoremap <expr> <F3> <SID>OpenPopup() |
| 22565 | 296 |
| 27162 | 297 Keep in mind that the expression may be evaluated when looking for |
|
24142
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
298 typeahead, before the previous command has been executed. For example: > |
|
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
299 func StoreColumn() |
|
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
300 let g:column = col('.') |
|
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
301 return 'x' |
|
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
302 endfunc |
|
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
303 nnoremap <expr> x StoreColumn() |
|
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
304 nmap ! f!x |
| 24278 | 305 You will notice that g:column has the value from before executing "f!", |
| 306 because "x" is evaluated before "f!" is executed. | |
|
24142
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
307 This can be solved by inserting <Ignore> before the character that is |
|
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
308 expression-mapped: > |
|
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
309 nmap ! f!<Ignore>x |
|
34acfef7f60c
patch 8.2.2612: col('.') may get outdated column value
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
310 |
|
27140
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
311 When defining a mapping in a |Vim9| script, the expression will be evaluated |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
312 in the context of that script. This means that script-local items can be |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
313 accessed in the expression. |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
314 |
| 721 | 315 Be very careful about side effects! The expression is evaluated while |
| 856 | 316 obtaining characters, you may very well make the command dysfunctional. |
| 317 For this reason the following is blocked: | |
| 1132 | 318 - Changing the buffer text |textlock|. |
| 319 - Editing another buffer. | |
| 320 - The |:normal| command. | |
| 321 - Moving the cursor is allowed, but it is restored afterwards. | |
| 856 | 322 If you want the mapping to do any of these let the returned characters do |
|
22862
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
323 that, or use a |<Cmd>| mapping instead. |
| 721 | 324 |
| 3153 | 325 You can use getchar(), it consumes typeahead if there is any. E.g., if you |
| 326 have these mappings: > | |
| 327 inoremap <expr> <C-L> nr2char(getchar()) | |
| 328 inoremap <expr> <C-L>x "foo" | |
| 329 If you now type CTRL-L nothing happens yet, Vim needs the next character to | |
| 330 decide what mapping to use. If you type 'x' the second mapping is used and | |
| 3224 | 331 "foo" is inserted. If you type any other key the first mapping is used, |
| 332 getchar() gets the typed key and returns it. | |
| 3153 | 333 |
| 721 | 334 Here is an example that inserts a list number that increases: > |
| 335 let counter = 0 | |
| 336 inoremap <expr> <C-L> ListItem() | |
| 337 inoremap <expr> <C-R> ListReset() | |
| 338 | |
| 339 func ListItem() | |
| 340 let g:counter += 1 | |
| 27903 | 341 return g:counter .. '. ' |
| 721 | 342 endfunc |
| 343 | |
| 344 func ListReset() | |
| 345 let g:counter = 0 | |
| 346 return '' | |
| 347 endfunc | |
| 348 | |
| 727 | 349 CTRL-L inserts the next number, CTRL-R resets the count. CTRL-R returns an |
| 721 | 350 empty string, so that nothing is inserted. |
| 7 | 351 |
| 22171 | 352 Note that using 0x80 as a single byte before other text does not work, it will |
| 353 be seen as a special key. | |
| 837 | 354 |
|
22862
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
355 *<Cmd>* *:map-cmd* |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
356 The special text <Cmd> begins a "command mapping", it executes the command |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
357 directly without changing modes. Where you might use ":...<CR>" in the |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
358 {rhs} of a mapping, you can instead use "<Cmd>...<CR>". |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
359 Example: > |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
360 noremap x <Cmd>echo mode(1)<CR> |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
361 < |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
362 This is more flexible than `:<C-U>` in Visual and Operator-pending mode, or |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
363 `<C-O>:` in Insert mode, because the commands are executed directly in the |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
364 current mode, instead of always going to Normal mode. Visual mode is |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
365 preserved, so tricks with |gv| are not needed. Commands can be invoked |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
366 directly in Command-line mode (which would otherwise require timer hacks). |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
367 Example of using <Cmd> halfway Insert mode: > |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
368 nnoremap <F3> aText <Cmd>echo mode(1)<CR> Added<Esc> |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
369 |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
370 Unlike <expr> mappings, there are no special restrictions on the <Cmd> |
| 22958 | 371 command: it is executed as if an (unrestricted) |autocommand| was invoked. |
|
22862
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
372 |
|
27140
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
373 *<ScriptCmd>* |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
374 <ScriptCmd> is like <Cmd> but sets the context to the script the mapping was |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
375 defined in, for the duration of the command execution. This is especially |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
376 useful for |Vim9| script. It also works to access an import, which is useful |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
377 in a plugin using an autoload script: > |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
378 vim9script |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
379 import autoload 'implementation.vim' as impl |
| 27162 | 380 nnoremap <F4> <ScriptCmd>impl.DoTheWork()<CR> |
|
27140
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
381 |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
382 No matter where <F4> is typed, the "impl" import will be found in the script |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
383 context of where the mapping was defined. And since it's an autoload import, |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
384 the "implementation.vim" script will only be loaded once <F4> is typed, not |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
385 when the mapping is defined. |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
386 |
|
22862
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
387 Note: |
|
27140
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
388 - Because <Cmd> and <ScriptCmd> avoid mode-changes it does not trigger |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
389 |CmdlineEnter| and |CmdlineLeave| events, because no user interaction is |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
390 expected. |
|
22862
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
391 - For the same reason, |keycodes| like <C-R><C-W> are interpreted as plain, |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
392 unmapped keys. |
| 22958 | 393 - The command is not echo'ed, no need for <silent>. |
| 26219 | 394 - The {rhs} is not subject to abbreviations nor to other mappings, even if the |
| 395 mapping is recursive. | |
| 22958 | 396 - In Visual mode you can use `line('v')` and `col('v')` to get one end of the |
| 397 Visual area, the cursor is at the other end. | |
| 29236 | 398 |
| 26779 | 399 *E1255* *E1136* |
|
27140
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
400 <Cmd> and <ScriptCmd> commands must terminate, that is, they must be followed |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
401 by <CR> in the {rhs} of the mapping definition. |Command-line| mode is never |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
402 entered. |
|
22862
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
403 |
|
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
404 *E1137* |
|
27140
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
405 <Cmd> and <ScriptCmd> commands can have only normal characters and cannot |
|
a9eeb18e749c
patch 8.2.4099: Vim9: cannot use Vim9 syntax in mapping
Bram Moolenaar <Bram@vim.org>
parents:
27036
diff
changeset
|
406 contain special characters like function keys. |
|
22862
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22565
diff
changeset
|
407 |
| 7 | 408 |
| 592 | 409 1.3 MAPPING AND MODES *:map-modes* |
| 1619 | 410 *mapmode-nvo* *mapmode-n* *mapmode-v* *mapmode-o* |
| 7 | 411 |
| 28010 | 412 There are seven sets of mappings |
| 7 | 413 - For Normal mode: When typing commands. |
| 414 - For Visual mode: When typing commands while the Visual area is highlighted. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
415 - For Select mode: like Visual mode but typing text replaces the selection. |
| 7 | 416 - For Operator-pending mode: When an operator is pending (after "d", "y", "c", |
| 1619 | 417 etc.). See below: |omap-info|. |
| 236 | 418 - For Insert mode. These are also used in Replace mode. |
| 7 | 419 - For Command-line mode: When entering a ":" or "/" command. |
| 28010 | 420 - For Terminal mode: When typing in a |:terminal| buffer. |
| 7 | 421 |
| 422 Special case: While typing a count for a command in Normal mode, mapping zero | |
| 423 is disabled. This makes it possible to map zero without making it impossible | |
| 424 to type a count with a zero. | |
| 425 | |
| 426 *map-overview* *map-modes* | |
| 5908 | 427 Overview of which map command works in which mode. More details below. |
| 428 COMMANDS MODES ~ | |
| 429 :map :noremap :unmap Normal, Visual, Select, Operator-pending | |
| 430 :nmap :nnoremap :nunmap Normal | |
| 431 :vmap :vnoremap :vunmap Visual and Select | |
| 432 :smap :snoremap :sunmap Select | |
| 433 :xmap :xnoremap :xunmap Visual | |
| 434 :omap :onoremap :ounmap Operator-pending | |
| 435 :map! :noremap! :unmap! Insert and Command-line | |
| 436 :imap :inoremap :iunmap Insert | |
| 437 :lmap :lnoremap :lunmap Insert, Command-line, Lang-Arg | |
| 438 :cmap :cnoremap :cunmap Command-line | |
|
12457
dfb8254aa735
patch 8.0.1108: cannot specify mappings for the terminal window
Christian Brabandt <cb@256bit.org>
parents:
12419
diff
changeset
|
439 :tmap :tnoremap :tunmap Terminal-Job |
| 7 | 440 |
| 24636 | 441 Same information in a table: |
| 442 *map-table* | |
| 443 Mode | Norm | Ins | Cmd | Vis | Sel | Opr | Term | Lang | ~ | |
| 444 Command +------+-----+-----+-----+-----+-----+------+------+ ~ | |
| 445 [nore]map | yes | - | - | yes | yes | yes | - | - | | |
| 446 n[nore]map | yes | - | - | - | - | - | - | - | | |
| 447 [nore]map! | - | yes | yes | - | - | - | - | - | | |
| 448 i[nore]map | - | yes | - | - | - | - | - | - | | |
| 449 c[nore]map | - | - | yes | - | - | - | - | - | | |
| 450 v[nore]map | - | - | - | yes | yes | - | - | - | | |
| 451 x[nore]map | - | - | - | yes | - | - | - | - | | |
| 452 s[nore]map | - | - | - | - | yes | - | - | - | | |
| 453 o[nore]map | - | - | - | - | - | yes | - | - | | |
| 454 t[nore]map | - | - | - | - | - | - | yes | - | | |
| 455 l[nore]map | - | yes | yes | - | - | - | - | yes | | |
| 456 | |
| 5908 | 457 |
| 458 COMMANDS MODES ~ | |
| 856 | 459 Normal Visual+Select Operator-pending ~ |
| 460 :map :noremap :unmap :mapclear yes yes yes | |
| 461 :nmap :nnoremap :nunmap :nmapclear yes - - | |
| 462 :vmap :vnoremap :vunmap :vmapclear - yes - | |
| 463 :omap :onoremap :ounmap :omapclear - - yes | |
| 788 | 464 |
| 826 | 465 :nunmap can also be used outside of a monastery. |
| 856 | 466 *mapmode-x* *mapmode-s* |
| 788 | 467 Some commands work both in Visual and Select mode, some in only one. Note |
| 468 that quite often "Visual" is mentioned where both Visual and Select mode | |
| 469 apply. |Select-mode-mapping| | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
470 NOTE: Mapping a printable character in Select mode may confuse the user. It's |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
471 better to explicitly use :xmap and :smap for printable characters. Or use |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
472 :sunmap after defining the mapping. |
| 788 | 473 |
| 5908 | 474 COMMANDS MODES ~ |
| 856 | 475 Visual Select ~ |
| 476 :vmap :vnoremap :vunmap :vmapclear yes yes | |
| 477 :xmap :xnoremap :xunmap :xmapclear yes - | |
| 478 :smap :snoremap :sunmap :smapclear - yes | |
| 7 | 479 |
| 663 | 480 *mapmode-ic* *mapmode-i* *mapmode-c* *mapmode-l* |
| 788 | 481 Some commands work both in Insert mode and Command-line mode, some not: |
| 482 | |
| 5908 | 483 COMMANDS MODES ~ |
| 7 | 484 Insert Command-line Lang-Arg ~ |
| 485 :map! :noremap! :unmap! :mapclear! yes yes - | |
| 486 :imap :inoremap :iunmap :imapclear yes - - | |
| 487 :cmap :cnoremap :cunmap :cmapclear - yes - | |
| 488 :lmap :lnoremap :lunmap :lmapclear yes* yes* yes* | |
| 489 | |
| 18594 | 490 * If 'iminsert' is 1, see |language-mapping| below. |
| 491 | |
| 7 | 492 The original Vi did not have separate mappings for |
| 493 Normal/Visual/Operator-pending mode and for Insert/Command-line mode. | |
| 494 Therefore the ":map" and ":map!" commands enter and display mappings for | |
| 495 several modes. In Vim you can use the ":nmap", ":vmap", ":omap", ":cmap" and | |
| 496 ":imap" commands to enter mappings for each mode separately. | |
| 497 | |
|
12457
dfb8254aa735
patch 8.0.1108: cannot specify mappings for the terminal window
Christian Brabandt <cb@256bit.org>
parents:
12419
diff
changeset
|
498 *mapmode-t* |
|
dfb8254aa735
patch 8.0.1108: cannot specify mappings for the terminal window
Christian Brabandt <cb@256bit.org>
parents:
12419
diff
changeset
|
499 The terminal mappings are used in a terminal window, when typing keys for the |
|
dfb8254aa735
patch 8.0.1108: cannot specify mappings for the terminal window
Christian Brabandt <cb@256bit.org>
parents:
12419
diff
changeset
|
500 job running in the terminal. See |terminal-typing|. |
|
dfb8254aa735
patch 8.0.1108: cannot specify mappings for the terminal window
Christian Brabandt <cb@256bit.org>
parents:
12419
diff
changeset
|
501 |
| 1619 | 502 *omap-info* |
| 503 Operator-pending mappings can be used to define a movement command that can be | |
| 14864 | 504 used with any operator. Simple example: > |
| 505 :omap { w | |
| 506 makes "y{" work like "yw" and "d{" like "dw". | |
| 1619 | 507 |
| 508 To ignore the starting cursor position and select different text, you can have | |
| 509 the omap start Visual mode to select the text to be operated upon. Example | |
| 510 that operates on a function name in the current line: > | |
| 511 onoremap <silent> F :<C-U>normal! 0f(hviw<CR> | |
| 512 The CTRL-U (<C-U>) is used to remove the range that Vim may insert. The | |
| 513 Normal mode commands find the first '(' character and select the first word | |
| 514 before it. That usually is the function name. | |
| 515 | |
| 7 | 516 To enter a mapping for Normal and Visual mode, but not Operator-pending mode, |
| 14864 | 517 first define it for all three modes, then unmap it for |
| 518 Operator-pending mode: > | |
| 7 | 519 :map xx something-difficult |
| 520 :ounmap xx | |
| 14864 | 521 |
| 7 | 522 Likewise for a mapping for Visual and Operator-pending mode or Normal and |
| 523 Operator-pending mode. | |
| 524 | |
| 525 *language-mapping* | |
| 526 ":lmap" defines a mapping that applies to: | |
| 527 - Insert mode | |
| 528 - Command-line mode | |
| 529 - when entering a search pattern | |
| 530 - the argument of the commands that accept a text character, such as "r" and | |
| 531 "f" | |
| 532 - for the input() line | |
| 533 Generally: Whenever a character is to be typed that is part of the text in the | |
| 534 buffer, not a Vim command character. "Lang-Arg" isn't really another mode, | |
| 535 it's just used here for this situation. | |
| 536 The simplest way to load a set of related language mappings is by using the | |
| 537 'keymap' option. See |45.5|. | |
| 538 In Insert mode and in Command-line mode the mappings can be disabled with | |
| 5340 | 539 the CTRL-^ command |i_CTRL-^| |c_CTRL-^|. These commands change the value of |
| 5294 | 540 the 'iminsert' option. When starting to enter a normal command line (not a |
| 541 search pattern) the mappings are disabled until a CTRL-^ is typed. The state | |
| 542 last used is remembered for Insert mode and Search patterns separately. The | |
| 543 state for Insert mode is also used when typing a character as an argument to | |
| 544 command like "f" or "t". | |
| 7 | 545 Language mappings will never be applied to already mapped characters. They |
| 546 are only used for typed characters. This assumes that the language mapping | |
| 547 was already done when typing the mapping. | |
| 548 | |
| 549 | |
| 592 | 550 1.4 LISTING MAPPINGS *map-listing* |
| 551 | |
| 7 | 552 When listing mappings the characters in the first two columns are: |
| 553 | |
| 554 CHAR MODE ~ | |
| 1132 | 555 <Space> Normal, Visual, Select and Operator-pending |
| 7 | 556 n Normal |
| 1132 | 557 v Visual and Select |
| 558 s Select | |
| 559 x Visual | |
| 7 | 560 o Operator-pending |
| 561 ! Insert and Command-line | |
| 562 i Insert | |
| 563 l ":lmap" mappings for Insert, Command-line and Lang-Arg | |
| 564 c Command-line | |
|
12481
bcd9b3e4a5c8
patch 8.0.1120: :tm means :tmap instead of :tmenu
Christian Brabandt <cb@256bit.org>
parents:
12457
diff
changeset
|
565 t Terminal-Job |
| 7 | 566 |
| 567 Just before the {rhs} a special character can appear: | |
| 568 * indicates that it is not remappable | |
| 569 & indicates that only script-local mappings are remappable | |
| 570 @ indicates a buffer-local mapping | |
| 571 | |
| 572 Everything from the first non-blank after {lhs} up to the end of the line | |
| 573 (or '|') is considered to be part of {rhs}. This allows the {rhs} to end | |
| 574 with a space. | |
| 575 | |
| 576 Note: When using mappings for Visual mode, you can use the "'<" mark, which | |
| 577 is the start of the last selected Visual area in the current buffer |'<|. | |
| 578 | |
|
10004
8061455d9179
commit https://github.com/vim/vim/commit/818078ddfbb8cc2546f697c5675a251d095722ec
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
579 The |:filter| command can be used to select what mappings to list. The |
|
8061455d9179
commit https://github.com/vim/vim/commit/818078ddfbb8cc2546f697c5675a251d095722ec
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
580 pattern is matched against the {lhs} and {rhs} in the raw form. |
|
8061455d9179
commit https://github.com/vim/vim/commit/818078ddfbb8cc2546f697c5675a251d095722ec
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
581 |
| 481 | 582 *:map-verbose* |
| 583 When 'verbose' is non-zero, listing a key map will also display where it was | |
| 584 last defined. Example: > | |
| 585 | |
| 586 :verbose map <C-W>* | |
| 587 n <C-W>* * <C-W><C-S>* | |
| 856 | 588 Last set from /home/abcd/.vimrc |
| 481 | 589 |
| 483 | 590 See |:verbose-cmd| for more information. |
| 481 | 591 |
| 592 | 592 |
| 593 1.5 MAPPING SPECIAL KEYS *:map-special-keys* | |
| 594 | |
| 595 There are three ways to map a special key: | |
| 596 1. The Vi-compatible method: Map the key code. Often this is a sequence that | |
| 597 starts with <Esc>. To enter a mapping like this you type ":map " and then | |
| 598 you have to type CTRL-V before hitting the function key. Note that when | |
| 599 the key code for the key is in the termcap (the t_ options), it will | |
| 600 automatically be translated into the internal code and become the second | |
| 601 way of mapping (unless the 'k' flag is included in 'cpoptions'). | |
| 602 2. The second method is to use the internal code for the function key. To | |
| 603 enter such a mapping type CTRL-K and then hit the function key, or use | |
| 604 the form "#1", "#2", .. "#9", "#0", "<Up>", "<S-Down>", "<S-F7>", etc. | |
| 605 (see table of keys |key-notation|, all keys from <Up> can be used). The | |
| 606 first ten function keys can be defined in two ways: Just the number, like | |
| 607 "#2", and with "<F>", like "<F2>". Both stand for function key 2. "#0" | |
| 608 refers to function key 10, defined with option 't_f10', which may be | |
| 609 function key zero on some keyboards. The <> form cannot be used when | |
| 610 'cpoptions' includes the '<' flag. | |
| 611 3. Use the termcap entry, with the form <t_xx>, where "xx" is the name of the | |
| 612 termcap entry. Any string entry can be used. For example: > | |
| 613 :map <t_F3> G | |
| 614 < Maps function key 13 to "G". This does not work if 'cpoptions' includes | |
| 615 the '<' flag. | |
| 616 | |
| 617 The advantage of the second and third method is that the mapping will work on | |
| 618 different terminals without modification (the function key will be | |
| 619 translated into the same internal code or the actual key code, no matter what | |
| 620 terminal you are using. The termcap must be correct for this to work, and you | |
| 621 must use the same mappings). | |
| 622 | |
| 623 DETAIL: Vim first checks if a sequence from the keyboard is mapped. If it | |
| 624 isn't the terminal key codes are tried (see |terminal-options|). If a | |
| 625 terminal code is found it is replaced with the internal code. Then the check | |
| 626 for a mapping is done again (so you can map an internal code to something | |
| 627 else). What is written into the script file depends on what is recognized. | |
| 628 If the terminal key code was recognized as a mapping the key code itself is | |
| 629 written to the script file. If it was recognized as a terminal code the | |
| 630 internal code is written to the script file. | |
| 631 | |
| 632 | |
| 633 1.6 SPECIAL CHARACTERS *:map-special-chars* | |
|
7597
3012eaddb6b2
commit https://github.com/vim/vim/commit/345efa013dc6d1754ba06e5596a26c48c9935937
Christian Brabandt <cb@256bit.org>
parents:
6447
diff
changeset
|
634 *map_backslash* *map-backslash* |
| 7 | 635 Note that only CTRL-V is mentioned here as a special character for mappings |
| 636 and abbreviations. When 'cpoptions' does not contain 'B', a backslash can | |
| 637 also be used like CTRL-V. The <> notation can be fully used then |<>|. But | |
| 638 you cannot use "<C-V>" like CTRL-V to escape the special meaning of what | |
| 639 follows. | |
| 640 | |
| 641 To map a backslash, or use a backslash literally in the {rhs}, the special | |
| 642 sequence "<Bslash>" can be used. This avoids the need to double backslashes | |
| 643 when using nested mappings. | |
| 644 | |
|
7597
3012eaddb6b2
commit https://github.com/vim/vim/commit/345efa013dc6d1754ba06e5596a26c48c9935937
Christian Brabandt <cb@256bit.org>
parents:
6447
diff
changeset
|
645 *map_CTRL-C* *map-CTRL-C* |
| 532 | 646 Using CTRL-C in the {lhs} is possible, but it will only work when Vim is |
| 647 waiting for a key, not when Vim is busy with something. When Vim is busy | |
| 648 CTRL-C interrupts/breaks the command. | |
| 649 When using the GUI version on MS-Windows CTRL-C can be mapped to allow a Copy | |
| 650 command to the clipboard. Use CTRL-Break to interrupt Vim. | |
| 7 | 651 |
|
7597
3012eaddb6b2
commit https://github.com/vim/vim/commit/345efa013dc6d1754ba06e5596a26c48c9935937
Christian Brabandt <cb@256bit.org>
parents:
6447
diff
changeset
|
652 *map_space_in_lhs* *map-space_in_lhs* |
| 7 | 653 To include a space in {lhs} precede it with a CTRL-V (type two CTRL-Vs for |
| 654 each space). | |
|
7597
3012eaddb6b2
commit https://github.com/vim/vim/commit/345efa013dc6d1754ba06e5596a26c48c9935937
Christian Brabandt <cb@256bit.org>
parents:
6447
diff
changeset
|
655 *map_space_in_rhs* *map-space_in_rhs* |
| 7 | 656 If you want a {rhs} that starts with a space, use "<Space>". To be fully Vi |
| 657 compatible (but unreadable) don't use the |<>| notation, precede {rhs} with a | |
| 658 single CTRL-V (you have to type CTRL-V two times). | |
|
7597
3012eaddb6b2
commit https://github.com/vim/vim/commit/345efa013dc6d1754ba06e5596a26c48c9935937
Christian Brabandt <cb@256bit.org>
parents:
6447
diff
changeset
|
659 *map_empty_rhs* *map-empty-rhs* |
| 7 | 660 You can create an empty {rhs} by typing nothing after a single CTRL-V (you |
| 661 have to type CTRL-V two times). Unfortunately, you cannot do this in a vimrc | |
| 662 file. | |
| 663 *<Nop>* | |
| 2826 | 664 An easier way to get a mapping that doesn't produce anything, is to use |
| 665 "<Nop>" for the {rhs}. This only works when the |<>| notation is enabled. | |
| 666 For example, to make sure that function key 8 does nothing at all: > | |
| 7 | 667 :map <F8> <Nop> |
| 668 :map! <F8> <Nop> | |
| 669 < | |
| 592 | 670 *map-multibyte* |
| 671 It is possible to map multibyte characters, but only the whole character. You | |
| 672 cannot map the first byte only. This was done to prevent problems in this | |
| 673 scenario: > | |
| 674 :set encoding=latin1 | |
| 675 :imap <M-C> foo | |
| 676 :set encoding=utf-8 | |
| 677 The mapping for <M-C> is defined with the latin1 encoding, resulting in a 0xc3 | |
| 13857 | 678 byte. If you type the character á (0xe1 <M-a>) in UTF-8 encoding this is the |
| 2826 | 679 two bytes 0xc3 0xa1. You don't want the 0xc3 byte to be mapped then or |
| 13857 | 680 otherwise it would be impossible to type the á character. |
| 592 | 681 |
| 7 | 682 *<Leader>* *mapleader* |
| 683 To define a mapping which uses the "mapleader" variable, the special string | |
| 684 "<Leader>" can be used. It is replaced with the string value of "mapleader". | |
| 685 If "mapleader" is not set or empty, a backslash is used instead. Example: > | |
| 686 :map <Leader>A oanother line<Esc> | |
| 687 Works like: > | |
| 688 :map \A oanother line<Esc> | |
| 689 But after: > | |
| 690 :let mapleader = "," | |
| 691 It works like: > | |
| 692 :map ,A oanother line<Esc> | |
| 693 | |
| 694 Note that the value of "mapleader" is used at the moment the mapping is | |
| 695 defined. Changing "mapleader" after that has no effect for already defined | |
| 696 mappings. | |
| 697 | |
| 698 *<LocalLeader>* *maplocalleader* | |
| 1619 | 699 <LocalLeader> is just like <Leader>, except that it uses "maplocalleader" |
| 700 instead of "mapleader". <LocalLeader> is to be used for mappings which are | |
| 701 local to a buffer. Example: > | |
| 3312 | 702 :map <buffer> <LocalLeader>A oanother line<Esc> |
| 7 | 703 < |
| 704 In a global plugin <Leader> should be used and in a filetype plugin | |
| 705 <LocalLeader>. "mapleader" and "maplocalleader" can be equal. Although, if | |
| 706 you make them different, there is a smaller chance of mappings from global | |
| 707 plugins to clash with mappings for filetype plugins. For example, you could | |
| 708 keep "mapleader" at the default backslash, and set "maplocalleader" to an | |
| 709 underscore. | |
| 710 | |
| 711 *map-<SID>* | |
| 712 In a script the special key name "<SID>" can be used to define a mapping | |
| 713 that's local to the script. See |<SID>| for details. | |
| 714 | |
| 715 *<Plug>* | |
| 716 The special key name "<Plug>" can be used for an internal mapping, which is | |
| 717 not to be matched with any key sequence. This is useful in plugins | |
| 718 |using-<Plug>|. | |
| 719 | |
| 28379 | 720 *<MouseMove>* |
| 721 The special key name "<MouseMove>" can be used to handle mouse movement. It | |
| 722 needs to be enabled with 'mousemoveevent'. Currently only works in the GUI. | |
| 28933 | 723 The |getmousepos()| function can be used to obtain the mouse position. |
| 28379 | 724 |
| 7 | 725 *<Char>* *<Char->* |
| 726 To map a character by its decimal, octal or hexadecimal number the <Char> | |
| 727 construct can be used: | |
| 728 <Char-123> character 123 | |
| 729 <Char-033> character 27 | |
| 730 <Char-0x7f> character 127 | |
| 3082 | 731 <S-Char-114> character 114 ('r') shifted ('R') |
| 21991 | 732 This is useful to specify a (multibyte) character in a 'keymap' file. |
| 7 | 733 Upper and lowercase differences are ignored. |
| 734 | |
| 735 *map-comments* | |
| 736 It is not possible to put a comment after these commands, because the '"' | |
| 11160 | 737 character is considered to be part of the {lhs} or {rhs}. However, one can |
| 738 use |", since this starts a new, empty command with a comment. | |
| 7 | 739 |
|
7597
3012eaddb6b2
commit https://github.com/vim/vim/commit/345efa013dc6d1754ba06e5596a26c48c9935937
Christian Brabandt <cb@256bit.org>
parents:
6447
diff
changeset
|
740 *map_bar* *map-bar* |
| 7 | 741 Since the '|' character is used to separate a map command from the next |
| 742 command, you will have to do something special to include a '|' in {rhs}. | |
| 743 There are three methods: | |
| 744 use works when example ~ | |
| 745 <Bar> '<' is not in 'cpoptions' :map _l :!ls <Bar> more^M | |
| 746 \| 'b' is not in 'cpoptions' :map _l :!ls \| more^M | |
| 747 ^V| always, in Vim and Vi :map _l :!ls ^V| more^M | |
| 748 | |
| 749 (here ^V stands for CTRL-V; to get one CTRL-V you have to type it twice; you | |
| 750 cannot use the <> notation "<C-V>" here). | |
| 751 | |
| 752 All three work when you use the default setting for 'cpoptions'. | |
| 753 | |
| 754 When 'b' is present in 'cpoptions', "\|" will be recognized as a mapping | |
| 755 ending in a '\' and then another command. This is Vi compatible, but | |
| 756 illogical when compared to other commands. | |
| 757 | |
|
7597
3012eaddb6b2
commit https://github.com/vim/vim/commit/345efa013dc6d1754ba06e5596a26c48c9935937
Christian Brabandt <cb@256bit.org>
parents:
6447
diff
changeset
|
758 *map_return* *map-return* |
| 7 | 759 When you have a mapping that contains an Ex command, you need to put a line |
| 760 terminator after it to have it executed. The use of <CR> is recommended for | |
| 761 this (see |<>|). Example: > | |
|
5692
80e5f9584b02
Update runtime files. Add Euphoria syntax files.
Bram Moolenaar <bram@vim.org>
parents:
5340
diff
changeset
|
762 :map _ls :!ls -l %:S<CR>:echo "the end"<CR> |
| 7 | 763 |
| 764 To avoid mapping of the characters you type in insert or Command-line mode, | |
| 765 type a CTRL-V first. The mapping in Insert mode is disabled if the 'paste' | |
| 766 option is on. | |
| 5239 | 767 *map-error* |
| 7 | 768 Note that when an error is encountered (that causes an error message or beep) |
| 769 the rest of the mapping is not executed. This is Vi-compatible. | |
| 770 | |
| 771 Note that the second character (argument) of the commands @zZtTfF[]rm'`"v | |
| 772 and CTRL-X is not mapped. This was done to be able to use all the named | |
| 773 registers and marks, even when the command with the same name has been | |
| 774 mapped. | |
| 775 | |
| 592 | 776 |
| 777 1.7 WHAT KEYS TO MAP *map-which-keys* | |
| 778 | |
| 7 | 779 If you are going to map something, you will need to choose which key(s) to use |
| 780 for the {lhs}. You will have to avoid keys that are used for Vim commands, | |
| 781 otherwise you would not be able to use those commands anymore. Here are a few | |
| 782 suggestions: | |
| 783 - Function keys <F2>, <F3>, etc.. Also the shifted function keys <S-F1>, | |
| 784 <S-F2>, etc. Note that <F1> is already used for the help command. | |
|
2324
0a258a67051d
In Visual mode with 'showcmd' display the number of bytes and characters.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
785 - Meta-keys (with the ALT key pressed). Depending on your keyboard accented |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
786 characters may be used as well. |:map-alt-keys| |
| 7 | 787 - Use the '_' or ',' character and then any other character. The "_" and "," |
| 788 commands do exist in Vim (see |_| and |,|), but you probably never use them. | |
| 789 - Use a key that is a synonym for another command. For example: CTRL-P and | |
| 790 CTRL-N. Use an extra character to allow more mappings. | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
791 - The key defined by <Leader> and one or more other keys. This is especially |
|
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
792 useful in scripts. |mapleader| |
| 7 | 793 |
| 794 See the file "index" for keys that are not used and thus can be mapped without | |
| 795 losing any builtin function. You can also use ":help {key}^D" to find out if | |
| 796 a key is used for some command. ({key} is the specific key you want to find | |
| 797 out about, ^D is CTRL-D). | |
| 798 | |
| 592 | 799 |
| 800 1.8 EXAMPLES *map-examples* | |
| 801 | |
| 7 | 802 A few examples (given as you type them, for "<CR>" you type four characters; |
| 803 the '<' flag must not be present in 'cpoptions' for this to work). > | |
| 804 | |
| 805 :map <F3> o#include | |
| 806 :map <M-g> /foo<CR>cwbar<Esc> | |
| 807 :map _x d/END/e<CR> | |
| 808 :map! qq quadrillion questions | |
| 1132 | 809 |
| 810 | |
| 811 Multiplying a count | |
| 812 | |
| 813 When you type a count before triggering a mapping, it's like the count was | |
| 814 typed before the {lhs}. For example, with this mapping: > | |
| 815 :map <F4> 3w | |
| 816 Typing 2<F4> will result in "23w". Thus not moving 2 * 3 words but 23 words. | |
| 817 If you want to multiply counts use the expression register: > | |
| 818 :map <F4> @='3w'<CR> | |
| 819 The part between quotes is the expression being executed. |@=| | |
| 820 | |
| 592 | 821 |
| 822 1.9 USING MAPPINGS *map-typing* | |
| 823 | |
| 7 | 824 Vim will compare what you type with the start of a mapped sequence. If there |
| 825 is an incomplete match, it will get more characters until there either is a | |
| 826 complete match or until there is no match at all. Example: If you map! "qq", | |
| 827 the first 'q' will not appear on the screen until you type another | |
| 828 character. This is because Vim cannot know if the next character will be a | |
| 829 'q' or not. If the 'timeout' option is on (which is the default) Vim will | |
| 830 only wait for one second (or as long as specified with the 'timeoutlen' | |
| 831 option). After that it assumes that the 'q' is to be interpreted as such. If | |
| 832 you type slowly, or your system is slow, reset the 'timeout' option. Then you | |
| 833 might want to set the 'ttimeout' option. | |
| 834 | |
| 12499 | 835 *map-precedence* |
| 4869 | 836 Buffer-local mappings (defined using |:map-<buffer>|) take precedence over |
| 837 global mappings. When a buffer-local mapping is the same as a global mapping, | |
| 838 Vim will use the buffer-local mapping. In addition, Vim will use a complete | |
| 5055 | 839 mapping immediately if it was defined with <nowait>, even if a longer mapping |
| 840 has the same prefix. For example, given the following two mappings: > | |
| 841 :map <buffer> <nowait> \a :echo "Local \a"<CR> | |
| 842 :map \abc :echo "Global \abc"<CR> | |
| 843 When typing \a the buffer-local mapping will be used immediately. Vim will | |
| 844 not wait for more characters to see if the user might be typing \abc. | |
| 4869 | 845 |
| 7 | 846 *map-keys-fails* |
| 588 | 847 There are situations where key codes might not be recognized: |
| 7 | 848 - Vim can only read part of the key code. Mostly this is only the first |
| 849 character. This happens on some Unix versions in an xterm. | |
| 850 - The key code is after character(s) that are mapped. E.g., "<F1><F1>" or | |
| 851 "g<F1>". | |
| 588 | 852 |
| 7 | 853 The result is that the key code is not recognized in this situation, and the |
| 588 | 854 mapping fails. There are two actions needed to avoid this problem: |
| 855 | |
| 7 | 856 - Remove the 'K' flag from 'cpoptions'. This will make Vim wait for the rest |
| 857 of the characters of the function key. | |
| 858 - When using <F1> to <F4> the actual key code generated may correspond to | |
| 859 <xF1> to <xF4>. There are mappings from <xF1> to <F1>, <xF2> to <F2>, etc., | |
| 860 but these are not recognized after another half a mapping. Make sure the | |
| 861 key codes for <F1> to <F4> are correct: > | |
| 862 :set <F1>=<type CTRL-V><type F1> | |
| 863 < Type the <F1> as four characters. The part after the "=" must be done with | |
| 864 the actual keys, not the literal text. | |
| 865 Another solution is to use the actual key code in the mapping for the second | |
| 866 special key: > | |
| 867 :map <F1><Esc>OP :echo "yes"<CR> | |
| 868 Don't type a real <Esc>, Vim will recognize the key code and replace it with | |
| 869 <F1> anyway. | |
| 870 | |
| 588 | 871 Another problem may be that when keeping ALT or Meta pressed the terminal |
| 872 prepends ESC instead of setting the 8th bit. See |:map-alt-keys|. | |
| 873 | |
| 7 | 874 *recursive_mapping* |
| 875 If you include the {lhs} in the {rhs} you have a recursive mapping. When | |
| 876 {lhs} is typed, it will be replaced with {rhs}. When the {lhs} which is | |
| 877 included in {rhs} is encountered it will be replaced with {rhs}, and so on. | |
| 878 This makes it possible to repeat a command an infinite number of times. The | |
| 879 only problem is that the only way to stop this is by causing an error. The | |
| 880 macros to solve a maze uses this, look there for an example. There is one | |
| 881 exception: If the {rhs} starts with {lhs}, the first character is not mapped | |
| 882 again (this is Vi compatible). | |
| 883 For example: > | |
| 884 :map ab abcd | |
| 885 will execute the "a" command and insert "bcd" in the text. The "ab" in the | |
| 886 {rhs} will not be mapped again. | |
| 887 | |
| 888 If you want to exchange the meaning of two keys you should use the :noremap | |
| 889 command. For example: > | |
| 890 :noremap k j | |
| 891 :noremap j k | |
| 892 This will exchange the cursor up and down commands. | |
| 893 | |
| 894 With the normal :map command, when the 'remap' option is on, mapping takes | |
| 895 place until the text is found not to be a part of a {lhs}. For example, if | |
| 896 you use: > | |
| 897 :map x y | |
| 898 :map y x | |
| 899 Vim will replace x with y, and then y with x, etc. When this has happened | |
| 900 'maxmapdepth' times (default 1000), Vim will give the error message | |
| 901 "recursive mapping". | |
| 902 | |
| 903 *:map-undo* | |
| 904 If you include an undo command inside a mapped sequence, this will bring the | |
| 905 text back in the state before executing the macro. This is compatible with | |
| 906 the original Vi, as long as there is only one undo command in the mapped | |
| 907 sequence (having two undo commands in a mapped sequence did not make sense | |
| 908 in the original Vi, you would get back the text before the first undo). | |
| 909 | |
| 910 | |
| 592 | 911 1.10 MAPPING ALT-KEYS *:map-alt-keys* |
| 588 | 912 |
| 913 In the GUI Vim handles the Alt key itself, thus mapping keys with ALT should | |
| 914 always work. But in a terminal Vim gets a sequence of bytes and has to figure | |
| 915 out whether ALT was pressed or not. | |
| 916 | |
|
18400
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
917 If the terminal supports the modifyOtherKeys mode and it has been enabled, |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
918 then Vim can recognize more key combinations, see |modifyOtherKeys| below. |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
919 |
| 588 | 920 By default Vim assumes that pressing the ALT key sets the 8th bit of a typed |
| 605 | 921 character. Most decent terminals can work that way, such as xterm, aterm and |
| 588 | 922 rxvt. If your <A-k> mappings don't work it might be that the terminal is |
| 923 prefixing the character with an ESC character. But you can just as well type | |
| 924 ESC before a character, thus Vim doesn't know what happened (except for | |
| 925 checking the delay between characters, which is not reliable). | |
| 926 | |
| 927 As of this writing, some mainstream terminals like gnome-terminal and konsole | |
| 928 use the ESC prefix. There doesn't appear a way to have them use the 8th bit | |
| 605 | 929 instead. Xterm should work well by default. Aterm and rxvt should work well |
| 930 when started with the "--meta8" argument. You can also tweak resources like | |
| 931 "metaSendsEscape", "eightBitInput" and "eightBitOutput". | |
| 588 | 932 |
| 933 On the Linux console, this behavior can be toggled with the "setmetamode" | |
| 934 command. Bear in mind that not using an ESC prefix could get you in trouble | |
| 935 with other programs. You should make sure that bash has the "convert-meta" | |
| 936 option set to "on" in order for your Meta keybindings to still work on it | |
| 937 (it's the default readline behavior, unless changed by specific system | |
| 938 configuration). For that, you can add the line: > | |
| 939 | |
| 940 set convert-meta on | |
| 941 | |
| 942 to your ~/.inputrc file. If you're creating the file, you might want to use: > | |
| 943 | |
| 944 $include /etc/inputrc | |
| 945 | |
| 946 as the first line, if that file exists on your system, to keep global options. | |
| 947 This may cause a problem for entering special characters, such as the umlaut. | |
| 948 Then you should use CTRL-V before that character. | |
| 949 | |
| 950 Bear in mind that convert-meta has been reported to have troubles when used in | |
| 951 UTF-8 locales. On terminals like xterm, the "metaSendsEscape" resource can be | |
| 952 toggled on the fly through the "Main Options" menu, by pressing Ctrl-LeftClick | |
| 953 on the terminal; that's a good last resource in case you want to send ESC when | |
| 11473 | 954 using other applications but not when inside Vim. |
| 588 | 955 |
| 592 | 956 |
|
18400
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
957 1.11 MAPPING IN modifyOtherKeys mode *modifyOtherKeys* |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
958 |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
959 Xterm and a few other terminals can be put in a mode where keys with modifiers |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
960 are sent with a special escape code. Vim recognizes these codes and can then |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
961 make a difference between CTRL-H and Backspace, even when Backspace sends the |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
962 character 8. And many more special keys. |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
963 |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
964 For xterm modifyOtherKeys is enabled in the builtin termcap entry. If this is |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
965 not used you can enable modifyOtherKeys with these lines in your vimrc: > |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
966 let &t_TI = "\<Esc>[>4;2m" |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
967 let &t_TE = "\<Esc>[>4;m" |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
968 |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
969 In case the modifyOtherKeys mode causes problems you can disable it: > |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
970 let &t_TI = "" |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
971 let &t_TE = "" |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
972 It does not take effect immediately. To have this work without restarting Vim |
| 18594 | 973 execute a shell command, e.g.: `!ls` Or put the lines in your |vimrc|. |
| 974 | |
| 975 When modifyOtherKeys is enabled you can map <C-[> and <C-S-{>: > | |
| 976 imap <C-[> [[[ | |
|
22526
6325ef9143bc
patch 8.2.1811: mapping Ctrl-key does not work for '{', '}' and '|'
Bram Moolenaar <Bram@vim.org>
parents:
22328
diff
changeset
|
977 imap <C-{> {{{ |
|
6325ef9143bc
patch 8.2.1811: mapping Ctrl-key does not work for '{', '}' and '|'
Bram Moolenaar <Bram@vim.org>
parents:
22328
diff
changeset
|
978 Without modifyOtherKeys <C-[> and <C-{> are indistinguishable from Esc. |
|
6325ef9143bc
patch 8.2.1811: mapping Ctrl-key does not work for '{', '}' and '|'
Bram Moolenaar <Bram@vim.org>
parents:
22328
diff
changeset
|
979 Note that <C-{> is used and not <C-S-[> or <C-S-{>. This works on most |
|
6325ef9143bc
patch 8.2.1811: mapping Ctrl-key does not work for '{', '}' and '|'
Bram Moolenaar <Bram@vim.org>
parents:
22328
diff
changeset
|
980 keyboards. Similarly, <C-}> is used instead of <C-S-]> or <C-S-}> and |
|
6325ef9143bc
patch 8.2.1811: mapping Ctrl-key does not work for '{', '}' and '|'
Bram Moolenaar <Bram@vim.org>
parents:
22328
diff
changeset
|
981 <C-|> instead of <C-S-\> or <C-S-|>. Note that '|' has a special meaning in a |
|
6325ef9143bc
patch 8.2.1811: mapping Ctrl-key does not work for '{', '}' and '|'
Bram Moolenaar <Bram@vim.org>
parents:
22328
diff
changeset
|
982 mapping, see |map-bar|. |
|
6325ef9143bc
patch 8.2.1811: mapping Ctrl-key does not work for '{', '}' and '|'
Bram Moolenaar <Bram@vim.org>
parents:
22328
diff
changeset
|
983 |
|
6325ef9143bc
patch 8.2.1811: mapping Ctrl-key does not work for '{', '}' and '|'
Bram Moolenaar <Bram@vim.org>
parents:
22328
diff
changeset
|
984 WARNING: if you map <C-[> you may very well break any key codes that start |
|
6325ef9143bc
patch 8.2.1811: mapping Ctrl-key does not work for '{', '}' and '|'
Bram Moolenaar <Bram@vim.org>
parents:
22328
diff
changeset
|
985 with Esc. Make sure it comes AFTER other mappings. |
|
18400
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
986 |
| 21499 | 987 A known side effect is that in Insert mode the raw escape sequence is inserted |
| 988 after the CTRL-V key. This can be used to check whether modifyOtherKeys is | |
| 989 enabled: In Insert mode type CTRL-SHIFT-V CTRL-V, if you get one byte then | |
| 990 modifyOtherKeys is off, if you get <1b>27;5;118~ then it is on. | |
|
18400
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
991 |
| 18594 | 992 When the 'esckeys' option is off, then modifyOtherKeys will be disabled in |
| 993 Insert mode to avoid every key with a modifier causing Insert mode to end. | |
| 994 | |
|
18400
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
995 |
|
f66fee58e7e2
patch 8.1.2194: modifyOtherKeys is not enabled by default
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
996 1.12 MAPPING AN OPERATOR *:map-operator* |
| 592 | 997 |
| 998 An operator is used before a {motion} command. To define your own operator | |
| 23164 | 999 you must create a mapping that first sets the 'operatorfunc' option and then |
| 592 | 1000 invoke the |g@| operator. After the user types the {motion} command the |
| 1001 specified function will be called. | |
| 1002 | |
| 626 | 1003 *g@* *E774* *E775* |
| 592 | 1004 g@{motion} Call the function set by the 'operatorfunc' option. |
| 1005 The '[ mark is positioned at the start of the text | |
| 1006 moved over by {motion}, the '] mark on the last | |
| 1007 character of the text. | |
| 1008 The function is called with one String argument: | |
| 1009 "line" {motion} was |linewise| | |
| 1010 "char" {motion} was |characterwise| | |
|
2324
0a258a67051d
In Visual mode with 'showcmd' display the number of bytes and characters.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
1011 "block" {motion} was |blockwise-visual| |
| 26708 | 1012 The type can be forced, see |forced-motion|. |
|
2570
71b56b4e7785
Make the references to features in the help more consistent. (Sylvain Hitier)
Bram Moolenaar <bram@vim.org>
parents:
2561
diff
changeset
|
1013 {not available when compiled without the |+eval| |
| 592 | 1014 feature} |
| 1015 | |
| 1016 Here is an example that counts the number of spaces with <F4>: > | |
| 1017 | |
| 22171 | 1018 nnoremap <expr> <F4> CountSpaces() |
| 1019 xnoremap <expr> <F4> CountSpaces() | |
| 1020 " doubling <F4> works on a line | |
| 1021 nnoremap <expr> <F4><F4> CountSpaces() .. '_' | |
| 592 | 1022 |
| 26708 | 1023 function CountSpaces(context = {}, type = '') abort |
| 22171 | 1024 if a:type == '' |
| 26708 | 1025 let context = #{ |
| 1026 \ dot_command: v:false, | |
| 1027 \ extend_block: '', | |
| 1028 \ virtualedit: [&l:virtualedit, &g:virtualedit], | |
| 1029 \ } | |
| 1030 let &operatorfunc = function('CountSpaces', [context]) | |
| 26591 | 1031 set virtualedit=block |
| 22171 | 1032 return 'g@' |
| 26591 | 1033 endif |
| 22171 | 1034 |
| 26708 | 1035 let save = #{ |
| 1036 \ clipboard: &clipboard, | |
| 1037 \ selection: &selection, | |
| 1038 \ virtualedit: [&l:virtualedit, &g:virtualedit], | |
| 1039 \ register: getreginfo('"'), | |
| 1040 \ visual_marks: [getpos("'<"), getpos("'>")], | |
| 1041 \ } | |
| 592 | 1042 |
| 22171 | 1043 try |
| 26591 | 1044 set clipboard= selection=inclusive virtualedit= |
| 26708 | 1045 let commands = #{ |
| 1046 \ line: "'[V']", | |
| 1047 \ char: "`[v`]", | |
| 1048 \ block: "`[\<C-V>`]", | |
| 1049 \ }[a:type] | |
| 1050 let [_, _, col, off] = getpos("']") | |
| 1051 if off != 0 | |
| 1052 let vcol = getline("'[")->strpart(0, col + off)->strdisplaywidth() | |
| 1053 if vcol >= [line("'["), '$']->virtcol() - 1 | |
| 1054 let a:context.extend_block = '$' | |
| 1055 else | |
| 1056 let a:context.extend_block = vcol .. '|' | |
| 1057 endif | |
| 1058 endif | |
| 1059 if a:context.extend_block != '' | |
| 1060 let commands ..= 'oO' .. a:context.extend_block | |
| 26591 | 1061 endif |
| 1062 let commands ..= 'y' | |
| 1063 execute 'silent noautocmd keepjumps normal! ' .. commands | |
| 1064 echomsg getreg('"')->count(' ') | |
| 22171 | 1065 finally |
| 26708 | 1066 call setreg('"', save.register) |
| 1067 call setpos("'<", save.visual_marks[0]) | |
| 1068 call setpos("'>", save.visual_marks[1]) | |
| 1069 let &clipboard = save.clipboard | |
| 1070 let &selection = save.selection | |
| 1071 let [&l:virtualedit, &g:virtualedit] = get(a:context.dot_command ? save : a:context, 'virtualedit') | |
| 1072 let a:context.dot_command = v:true | |
| 22171 | 1073 endtry |
| 1074 endfunction | |
| 592 | 1075 |
| 22171 | 1076 An <expr> mapping is used to be able to fetch any prefixed count and register. |
| 1077 This also avoids using a command line, which would trigger CmdlineEnter and | |
| 1078 CmdlineLeave autocommands. | |
| 592 | 1079 |
| 1080 Note that the 'selection' option is temporarily set to "inclusive" to be able | |
| 1081 to yank exactly the right text by using Visual mode from the '[ to the '] | |
| 1082 mark. | |
| 1083 | |
| 22171 | 1084 Also note that the 'clipboard' option is temporarily emptied to avoid |
| 1085 clobbering the `"*` or `"+` registers, if its value contains the item `unnamed` | |
| 1086 or `unnamedplus`. | |
| 592 | 1087 |
| 26050 | 1088 The `mode()` function will return the state as it will be after applying the |
| 1089 operator. | |
| 1090 | |
|
26175
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1091 Here is an example for using a lambda function to create a normal-mode |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1092 operator to add quotes around text in the current line: > |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1093 |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1094 nnoremap <F4> <Cmd>let &opfunc='{t -> |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1095 \ getline(".") |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1096 \ ->split("\\zs") |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1097 \ ->insert("\"", col("'']")) |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1098 \ ->insert("\"", col("''[") - 1) |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1099 \ ->join("") |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1100 \ ->setline(".")}'<CR>g@ |
|
6b4f017d7005
patch 8.2.3619: cannot use a lambda for 'operatorfunc'
Bram Moolenaar <Bram@vim.org>
parents:
26148
diff
changeset
|
1101 |
| 7 | 1102 ============================================================================== |
| 1103 2. Abbreviations *abbreviations* *Abbreviations* | |
| 1104 | |
| 1105 Abbreviations are used in Insert mode, Replace mode and Command-line mode. | |
| 1106 If you enter a word that is an abbreviation, it is replaced with the word it | |
| 1107 stands for. This can be used to save typing for often used long words. And | |
| 1108 you can use it to automatically correct obvious spelling errors. | |
| 1109 Examples: | |
| 1110 | |
| 1190 | 1111 :iab ms Microsoft |
| 7 | 1112 :iab tihs this |
| 1113 | |
| 1114 There are three types of abbreviations: | |
| 1115 | |
| 1116 full-id The "full-id" type consists entirely of keyword characters (letters | |
| 1117 and characters from 'iskeyword' option). This is the most common | |
| 1118 abbreviation. | |
| 1119 | |
| 1120 Examples: "foo", "g3", "-1" | |
| 1121 | |
| 1122 end-id The "end-id" type ends in a keyword character, but all the other | |
| 1123 characters are not keyword characters. | |
| 1124 | |
| 1125 Examples: "#i", "..f", "$/7" | |
| 1126 | |
| 1127 non-id The "non-id" type ends in a non-keyword character, the other | |
| 1236 | 1128 characters may be of any type, excluding space and tab. {this type |
| 7 | 1129 is not supported by Vi} |
| 1130 | |
| 1131 Examples: "def#", "4/7$" | |
| 1132 | |
| 1133 Examples of strings that cannot be abbreviations: "a.b", "#def", "a b", "_$r" | |
| 1134 | |
| 1135 An abbreviation is only recognized when you type a non-keyword character. | |
| 1136 This can also be the <Esc> that ends insert mode or the <CR> that ends a | |
| 1137 command. The non-keyword character which ends the abbreviation is inserted | |
| 1138 after the expanded abbreviation. An exception to this is the character <C-]>, | |
| 1139 which is used to expand an abbreviation without inserting any extra | |
| 1140 characters. | |
| 1141 | |
| 1142 Example: > | |
| 1143 :ab hh hello | |
| 1144 < "hh<Space>" is expanded to "hello<Space>" | |
| 1145 "hh<C-]>" is expanded to "hello" | |
| 1146 | |
| 1147 The characters before the cursor must match the abbreviation. Each type has | |
| 1148 an additional rule: | |
| 1149 | |
| 1150 full-id In front of the match is a non-keyword character, or this is where | |
| 1151 the line or insertion starts. Exception: When the abbreviation is | |
| 1152 only one character, it is not recognized if there is a non-keyword | |
| 13937 | 1153 character in front of it, other than a space or a tab. However, for |
| 1154 the command line "'<,'>" (or any other marks) is ignored, as if the | |
| 1155 command line starts after it. | |
| 7 | 1156 |
| 1236 | 1157 end-id In front of the match is a keyword character, or a space or a tab, |
| 7 | 1158 or this is where the line or insertion starts. |
| 1159 | |
| 1236 | 1160 non-id In front of the match is a space, tab or the start of the line or |
| 7 | 1161 the insertion. |
| 1162 | |
| 1163 Examples: ({CURSOR} is where you type a non-keyword character) > | |
| 1164 :ab foo four old otters | |
| 1165 < " foo{CURSOR}" is expanded to " four old otters" | |
| 1166 " foobar{CURSOR}" is not expanded | |
| 1167 "barfoo{CURSOR}" is not expanded | |
| 1168 > | |
| 1169 :ab #i #include | |
| 1170 < "#i{CURSOR}" is expanded to "#include" | |
| 1171 ">#i{CURSOR}" is not expanded | |
| 1172 > | |
| 42 | 1173 :ab ;; <endofline> |
| 7 | 1174 < "test;;" is not expanded |
| 1175 "test ;;" is expanded to "test <endofline>" | |
| 1176 | |
|
6292
31f7581068a9
Update runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
6259
diff
changeset
|
1177 To avoid the abbreviation in Insert mode: Type CTRL-V before the character |
|
31f7581068a9
Update runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
6259
diff
changeset
|
1178 that would trigger the abbreviation. E.g. CTRL-V <Space>. Or type part of |
|
31f7581068a9
Update runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
6259
diff
changeset
|
1179 the abbreviation, exit insert mode with <Esc>, re-enter insert mode with "a" |
|
31f7581068a9
Update runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
6259
diff
changeset
|
1180 and type the rest. |
|
31f7581068a9
Update runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
6259
diff
changeset
|
1181 |
| 7 | 1182 To avoid the abbreviation in Command-line mode: Type CTRL-V twice somewhere in |
| 1183 the abbreviation to avoid it to be replaced. A CTRL-V in front of a normal | |
| 1184 character is mostly ignored otherwise. | |
| 1185 | |
| 1186 It is possible to move the cursor after an abbreviation: > | |
| 1187 :iab if if ()<Left> | |
| 1188 This does not work if 'cpoptions' includes the '<' flag. |<>| | |
| 1189 | |
| 1190 You can even do more complicated things. For example, to consume the space | |
| 1191 typed after an abbreviation: > | |
| 1192 func Eatchar(pat) | |
| 685 | 1193 let c = nr2char(getchar(0)) |
| 7 | 1194 return (c =~ a:pat) ? '' : c |
| 1195 endfunc | |
| 1196 iabbr <silent> if if ()<Left><C-R>=Eatchar('\s')<CR> | |
| 1197 | |
| 1198 There are no default abbreviations. | |
| 1199 | |
| 1200 Abbreviations are never recursive. You can use ":ab f f-o-o" without any | |
| 1201 problem. But abbreviations can be mapped. {some versions of Vi support | |
| 1202 recursive abbreviations, for no apparent reason} | |
| 1203 | |
| 1204 Abbreviations are disabled if the 'paste' option is on. | |
| 1205 | |
| 1206 *:abbreviate-local* *:abbreviate-<buffer>* | |
| 1207 Just like mappings, abbreviations can be local to a buffer. This is mostly | |
| 1208 used in a |filetype-plugin| file. Example for a C plugin file: > | |
| 1209 :abb <buffer> FF for (i = 0; i < ; ++i) | |
| 1210 < | |
| 1211 *:ab* *:abbreviate* | |
| 1212 :ab[breviate] list all abbreviations. The character in the first | |
| 1213 column indicates the mode where the abbreviation is | |
| 1214 used: 'i' for insert mode, 'c' for Command-line | |
| 1215 mode, '!' for both. These are the same as for | |
| 1216 mappings, see |map-listing|. | |
| 1217 | |
| 502 | 1218 *:abbreviate-verbose* |
| 1219 When 'verbose' is non-zero, listing an abbreviation will also display where it | |
| 1220 was last defined. Example: > | |
| 1221 | |
| 1222 :verbose abbreviate | |
| 856 | 1223 ! teh the |
| 502 | 1224 Last set from /home/abcd/vim/abbr.vim |
| 1225 | |
| 1226 See |:verbose-cmd| for more information. | |
| 1227 | |
| 7 | 1228 :ab[breviate] {lhs} list the abbreviations that start with {lhs} |
| 1229 You may need to insert a CTRL-V (type it twice) to | |
| 1230 avoid that a typed {lhs} is expanded, since | |
| 1231 command-line abbreviations apply here. | |
| 1232 | |
| 2908 | 1233 :ab[breviate] [<expr>] [<buffer>] {lhs} {rhs} |
| 7 | 1234 add abbreviation for {lhs} to {rhs}. If {lhs} already |
| 1235 existed it is replaced with the new {rhs}. {rhs} may | |
| 1236 contain spaces. | |
| 838 | 1237 See |:map-<expr>| for the optional <expr> argument. |
| 2908 | 1238 See |:map-<buffer>| for the optional <buffer> argument. |
| 7 | 1239 |
| 1240 *:una* *:unabbreviate* | |
| 18928 | 1241 :una[bbreviate] [<buffer>] {lhs} |
| 1242 Remove abbreviation for {lhs} from the list. If none | |
| 7 | 1243 is found, remove abbreviations in which {lhs} matches |
| 1244 with the {rhs}. This is done so that you can even | |
| 1245 remove abbreviations after expansion. To avoid | |
| 1246 expansion insert a CTRL-V (type it twice). | |
| 1247 | |
| 1248 *:norea* *:noreabbrev* | |
| 2908 | 1249 :norea[bbrev] [<expr>] [<buffer>] [lhs] [rhs] |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1250 Same as ":ab", but no remapping for this {rhs}. |
| 7 | 1251 |
| 16944 | 1252 *:ca* *:cab* *:cabbrev* |
| 2908 | 1253 :ca[bbrev] [<expr>] [<buffer>] [lhs] [rhs] |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1254 Same as ":ab", but for Command-line mode only. |
| 7 | 1255 |
| 1256 *:cuna* *:cunabbrev* | |
| 18928 | 1257 :cuna[bbrev] [<buffer>] {lhs} |
| 1258 Same as ":una", but for Command-line mode only. | |
| 7 | 1259 |
| 1260 *:cnorea* *:cnoreabbrev* | |
| 2908 | 1261 :cnorea[bbrev] [<expr>] [<buffer>] [lhs] [rhs] |
| 7 | 1262 same as ":ab", but for Command-line mode only and no |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1263 remapping for this {rhs} |
| 7 | 1264 |
| 1265 *:ia* *:iabbrev* | |
| 2908 | 1266 :ia[bbrev] [<expr>] [<buffer>] [lhs] [rhs] |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1267 Same as ":ab", but for Insert mode only. |
| 7 | 1268 |
| 1269 *:iuna* *:iunabbrev* | |
| 18928 | 1270 :iuna[bbrev] [<buffer>] {lhs} |
| 1271 Same as ":una", but for insert mode only. | |
| 7 | 1272 |
| 1273 *:inorea* *:inoreabbrev* | |
| 2908 | 1274 :inorea[bbrev] [<expr>] [<buffer>] [lhs] [rhs] |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1275 Same as ":ab", but for Insert mode only and no |
|
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1276 remapping for this {rhs}. |
| 7 | 1277 |
| 1278 *:abc* *:abclear* | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1279 :abc[lear] [<buffer>] Remove all abbreviations. |
| 7 | 1280 |
| 1281 *:iabc* *:iabclear* | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1282 :iabc[lear] [<buffer>] Remove all abbreviations for Insert mode. |
| 7 | 1283 |
| 1284 *:cabc* *:cabclear* | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1285 :cabc[lear] [<buffer>] Remove all abbreviations for Command-line mode. |
| 7 | 1286 |
| 1287 *using_CTRL-V* | |
| 1288 It is possible to use special characters in the rhs of an abbreviation. | |
| 1289 CTRL-V has to be used to avoid the special meaning of most non printable | |
| 1290 characters. How many CTRL-Vs need to be typed depends on how you enter the | |
| 1291 abbreviation. This also applies to mappings. Let's use an example here. | |
| 1292 | |
| 1293 Suppose you want to abbreviate "esc" to enter an <Esc> character. When you | |
| 1294 type the ":ab" command in Vim, you have to enter this: (here ^V is a CTRL-V | |
| 1295 and ^[ is <Esc>) | |
| 1296 | |
| 1297 You type: ab esc ^V^V^V^V^V^[ | |
| 1298 | |
| 1299 All keyboard input is subjected to ^V quote interpretation, so | |
| 1300 the first, third, and fifth ^V characters simply allow the second, | |
| 1301 and fourth ^Vs, and the ^[, to be entered into the command-line. | |
| 1302 | |
| 1303 You see: ab esc ^V^V^[ | |
| 1304 | |
| 1305 The command-line contains two actual ^Vs before the ^[. This is | |
| 1306 how it should appear in your .exrc file, if you choose to go that | |
| 1307 route. The first ^V is there to quote the second ^V; the :ab | |
| 1308 command uses ^V as its own quote character, so you can include quoted | |
| 42 | 1309 whitespace or the | character in the abbreviation. The :ab command |
| 7 | 1310 doesn't do anything special with the ^[ character, so it doesn't need |
| 1311 to be quoted. (Although quoting isn't harmful; that's why typing 7 | |
| 1312 [but not 8!] ^Vs works.) | |
| 1313 | |
| 1314 Stored as: esc ^V^[ | |
| 1315 | |
| 1316 After parsing, the abbreviation's short form ("esc") and long form | |
| 1317 (the two characters "^V^[") are stored in the abbreviation table. | |
| 1318 If you give the :ab command with no arguments, this is how the | |
| 1319 abbreviation will be displayed. | |
| 1320 | |
| 1321 Later, when the abbreviation is expanded because the user typed in | |
| 1322 the word "esc", the long form is subjected to the same type of | |
| 1323 ^V interpretation as keyboard input. So the ^V protects the ^[ | |
| 42 | 1324 character from being interpreted as the "exit Insert mode" character. |
| 7 | 1325 Instead, the ^[ is inserted into the text. |
| 1326 | |
| 1327 Expands to: ^[ | |
| 1328 | |
| 1329 [example given by Steve Kirkendall] | |
| 1330 | |
| 1331 ============================================================================== | |
| 1332 3. Local mappings and functions *script-local* | |
| 1333 | |
| 1334 When using several Vim script files, there is the danger that mappings and | |
| 1335 functions used in one script use the same name as in other scripts. To avoid | |
| 1336 this, they can be made local to the script. | |
| 1337 | |
| 1338 *<SID>* *<SNR>* *E81* | |
| 1339 The string "<SID>" can be used in a mapping or menu. This requires that the | |
| 1340 '<' flag is not present in 'cpoptions'. | |
| 1341 When executing the map command, Vim will replace "<SID>" with the special | |
| 1342 key code <SNR>, followed by a number that's unique for the script, and an | |
| 1343 underscore. Example: > | |
| 1344 :map <SID>Add | |
| 1345 could define a mapping "<SNR>23_Add". | |
| 1346 | |
| 1347 When defining a function in a script, "s:" can be prepended to the name to | |
| 28517 | 1348 make it local to the script (in |Vim9| script functions without a prefix are |
| 1349 local to the script). But when a mapping is executed from outside of | |
| 7 | 1350 the script, it doesn't know in which script the function was defined. To |
| 1351 avoid this problem, use "<SID>" instead of "s:". The same translation is done | |
| 1352 as for mappings. This makes it possible to define a call to the function in | |
| 42 | 1353 a mapping. |
| 7 | 1354 |
| 1355 When a local function is executed, it runs in the context of the script it was | |
| 1356 defined in. This means that new functions and mappings it defines can also | |
| 1357 use "s:" or "<SID>" and it will use the same unique number as when the | |
| 1358 function itself was defined. Also, the "s:var" local script variables can be | |
| 1359 used. | |
| 1360 | |
| 1361 When executing an autocommand or a user command, it will run in the context of | |
| 1362 the script it was defined in. This makes it possible that the command calls a | |
| 1363 local function or uses a local mapping. | |
| 1364 | |
|
21594
5daca8504c63
patch 8.2.1347: cannot easily get the script ID
Bram Moolenaar <Bram@vim.org>
parents:
21499
diff
changeset
|
1365 In case the value is used in a context where <SID> cannot be correctly |
|
5daca8504c63
patch 8.2.1347: cannot easily get the script ID
Bram Moolenaar <Bram@vim.org>
parents:
21499
diff
changeset
|
1366 expanded, use the expand() function: > |
|
5daca8504c63
patch 8.2.1347: cannot easily get the script ID
Bram Moolenaar <Bram@vim.org>
parents:
21499
diff
changeset
|
1367 let &includexpr = expand('<SID>') .. 'My_includeexpr()' |
|
5daca8504c63
patch 8.2.1347: cannot easily get the script ID
Bram Moolenaar <Bram@vim.org>
parents:
21499
diff
changeset
|
1368 |
| 7 | 1369 Otherwise, using "<SID>" outside of a script context is an error. |
| 1370 | |
| 1371 If you need to get the script number to use in a complicated script, you can | |
| 625 | 1372 use this function: > |
| 22958 | 1373 func s:ScriptNumber() |
| 1374 return matchstr(expand('<SID>'), '<SNR>\zs\d\+\ze_') | |
| 1375 endfunc | |
| 7 | 1376 |
| 1377 The "<SNR>" will be shown when listing functions and mappings. This is useful | |
| 1378 to find out what they are defined to. | |
| 1379 | |
| 1380 The |:scriptnames| command can be used to see which scripts have been sourced | |
| 1381 and what their <SNR> number is. | |
| 1382 | |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1383 This is all {not available when compiled without the |+eval| feature}. |
| 7 | 1384 |
| 1385 ============================================================================== | |
| 1386 4. User-defined commands *user-commands* | |
| 1387 | |
| 236 | 1388 It is possible to define your own Ex commands. A user-defined command can act |
| 7 | 1389 just like a built-in command (it can have a range or arguments, arguments can |
| 1390 be completed as filenames or buffer names, etc), except that when the command | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
1391 is executed, it is transformed into a normal Ex command and then executed. |
| 7 | 1392 |
| 1393 For starters: See section |40.2| in the user manual. | |
| 1394 | |
| 2642 | 1395 *E183* *E841* *user-cmd-ambiguous* |
| 7 | 1396 All user defined commands must start with an uppercase letter, to avoid |
| 2642 | 1397 confusion with builtin commands. Exceptions are these builtin commands: |
| 1398 :Next | |
| 1399 :X | |
| 1400 They cannot be used for a user defined command. ":Print" is also an existing | |
| 1401 command, but it is deprecated and can be overruled. | |
| 1402 | |
| 1403 The other characters of the user command can be uppercase letters, lowercase | |
| 1404 letters or digits. When using digits, note that other commands that take a | |
| 1405 numeric argument may become ambiguous. For example, the command ":Cc2" could | |
| 1406 be the user command ":Cc2" without an argument, or the command ":Cc" with | |
| 1407 argument "2". It is advised to put a space between the command name and the | |
| 1408 argument to avoid these problems. | |
| 7 | 1409 |
| 236 | 1410 When using a user-defined command, the command can be abbreviated. However, if |
| 1411 an abbreviation is not unique, an error will be issued. Furthermore, a | |
| 7 | 1412 built-in command will always take precedence. |
| 1413 | |
| 1414 Example: > | |
| 1415 :command Rename ... | |
| 1416 :command Renumber ... | |
| 1417 :Rena " Means "Rename" | |
| 1418 :Renu " Means "Renumber" | |
| 1419 :Ren " Error - ambiguous | |
| 1420 :command Paste ... | |
| 1421 :P " The built-in :Print | |
| 1422 | |
| 1423 It is recommended that full names for user-defined commands are used in | |
| 1424 scripts. | |
| 1425 | |
| 1426 :com[mand] *:com* *:command* | |
| 236 | 1427 List all user-defined commands. When listing commands, |
|
16399
47d6e874955c
patch 8.1.1204: output of :command with address completion is not nice
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1428 the characters in the first columns are: |
| 7 | 1429 ! Command has the -bang attribute |
| 1430 " Command has the -register attribute | |
|
16399
47d6e874955c
patch 8.1.1204: output of :command with address completion is not nice
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1431 | Command has the -bar attribute |
| 7 | 1432 b Command is local to current buffer |
| 1433 (see below for details on attributes) | |
|
10004
8061455d9179
commit https://github.com/vim/vim/commit/818078ddfbb8cc2546f697c5675a251d095722ec
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
1434 The list can be filtered on command name with |
|
8061455d9179
commit https://github.com/vim/vim/commit/818078ddfbb8cc2546f697c5675a251d095722ec
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
1435 |:filter|, e.g., to list all commands with "Pyth" in |
|
8061455d9179
commit https://github.com/vim/vim/commit/818078ddfbb8cc2546f697c5675a251d095722ec
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
1436 the name: > |
|
8061455d9179
commit https://github.com/vim/vim/commit/818078ddfbb8cc2546f697c5675a251d095722ec
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
1437 filter Pyth command |
| 7 | 1438 |
| 1439 :com[mand] {cmd} List the user-defined commands that start with {cmd} | |
| 1440 | |
| 482 | 1441 *:command-verbose* |
| 1442 When 'verbose' is non-zero, listing a command will also display where it was | |
| 27321 | 1443 last defined and any completion argument. Example: > |
| 482 | 1444 |
| 1445 :verbose command TOhtml | |
| 856 | 1446 < Name Args Range Complete Definition ~ |
| 1447 TOhtml 0 % :call Convert2HTML(<line1>, <line2>) ~ | |
| 1448 Last set from /usr/share/vim/vim-7.0/plugin/tohtml.vim ~ | |
| 1449 | |
| 483 | 1450 See |:verbose-cmd| for more information. |
| 482 | 1451 |
| 7 | 1452 *E174* *E182* |
| 23164 | 1453 :com[mand][!] [{attr}...] {cmd} {repl} |
| 7 | 1454 Define a user command. The name of the command is |
| 23164 | 1455 {cmd} and its replacement text is {repl}. The |
| 1456 command's attributes (see below) are {attr}. If the | |
| 1457 command already exists, an error is reported, unless a | |
| 1458 ! is specified, in which case the command is | |
| 1459 redefined. There is one exception: When sourcing a | |
| 1460 script again, a command that was previously defined in | |
| 1461 that script will be silently replaced. | |
|
15125
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1462 |
| 7 | 1463 |
| 1464 :delc[ommand] {cmd} *:delc* *:delcommand* *E184* | |
| 1465 Delete the user-defined command {cmd}. | |
| 1466 | |
|
25796
60e4892dfa45
patch 8.2.3433: :delcommand does not take a -buffer option
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
1467 :delc[ommand] -buffer {cmd} *E1237* |
|
60e4892dfa45
patch 8.2.3433: :delcommand does not take a -buffer option
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
1468 Delete the user-defined command {cmd} that was defined |
|
60e4892dfa45
patch 8.2.3433: :delcommand does not take a -buffer option
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
1469 for the current buffer. |
|
60e4892dfa45
patch 8.2.3433: :delcommand does not take a -buffer option
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
1470 |
| 7 | 1471 :comc[lear] *:comc* *:comclear* |
| 1472 Delete all user-defined commands. | |
| 1473 | |
|
15125
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1474 |
|
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1475 Command attributes ~ |
| 28010 | 1476 *command-attributes* |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
1477 User-defined commands are treated by Vim just like any other Ex commands. They |
| 236 | 1478 can have arguments, or have a range specified. Arguments are subject to |
| 1479 completion as filenames, buffers, etc. Exactly how this works depends upon the | |
| 7 | 1480 command's attributes, which are specified when the command is defined. |
| 1481 | |
| 1482 There are a number of attributes, split into four categories: argument | |
| 236 | 1483 handling, completion behavior, range handling, and special cases. The |
| 7 | 1484 attributes are described below, by category. |
| 1485 | |
| 1486 | |
|
15125
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1487 Argument handling ~ |
|
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1488 *E175* *E176* *:command-nargs* |
| 7 | 1489 By default, a user defined command will take no arguments (and an error is |
| 236 | 1490 reported if any are supplied). However, it is possible to specify that the |
| 1491 command can take arguments, using the -nargs attribute. Valid cases are: | |
| 7 | 1492 |
| 1493 -nargs=0 No arguments are allowed (the default) | |
| 15194 | 1494 -nargs=1 Exactly one argument is required, it includes spaces |
| 2826 | 1495 -nargs=* Any number of arguments are allowed (0, 1, or many), |
| 1496 separated by white space | |
| 7 | 1497 -nargs=? 0 or 1 arguments are allowed |
| 1498 -nargs=+ Arguments must be supplied, but any number are allowed | |
| 1499 | |
| 1236 | 1500 Arguments are considered to be separated by (unescaped) spaces or tabs in this |
| 2826 | 1501 context, except when there is one argument, then the white space is part of |
| 1502 the argument. | |
| 7 | 1503 |
| 1504 Note that arguments are used as text, not as expressions. Specifically, | |
| 1505 "s:var" will use the script-local variable in the script where the command was | |
| 1506 defined, not where it is invoked! Example: | |
| 1507 script1.vim: > | |
| 1508 :let s:error = "None" | |
| 1509 :command -nargs=1 Error echoerr <args> | |
| 1510 < script2.vim: > | |
| 1511 :source script1.vim | |
| 1512 :let s:error = "Wrong!" | |
| 1513 :Error s:error | |
| 1619 | 1514 Executing script2.vim will result in "None" being echoed. Not what you |
| 7 | 1515 intended! Calling a function may be an alternative. |
| 1516 | |
|
15125
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1517 |
|
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1518 Completion behavior ~ |
| 15194 | 1519 *:command-completion* *E179* *E180* *E181* |
|
15125
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1520 *:command-complete* |
| 7 | 1521 By default, the arguments of user defined commands do not undergo completion. |
| 1522 However, by specifying one or the other of the following attributes, argument | |
| 1523 completion can be enabled: | |
| 1524 | |
|
13551
1fd0f8392946
patch 8.0.1649: no completion for argument list commands
Christian Brabandt <cb@256bit.org>
parents:
12559
diff
changeset
|
1525 -complete=arglist file names in argument list |
| 7 | 1526 -complete=augroup autocmd groups |
| 1527 -complete=buffer buffer names | |
| 3503 | 1528 -complete=behave :behave suboptions |
| 2970 | 1529 -complete=color color schemes |
| 7 | 1530 -complete=command Ex command (and arguments) |
| 2970 | 1531 -complete=compiler compilers |
| 2596 | 1532 -complete=cscope |:cscope| suboptions |
| 7 | 1533 -complete=dir directory names |
| 1534 -complete=environment environment variable names | |
| 1535 -complete=event autocommand events | |
| 1536 -complete=expression Vim expression | |
| 1537 -complete=file file and directory names | |
| 2970 | 1538 -complete=file_in_path file and directory names in |'path'| |
|
2444
3fbd9bce03f1
Support syntax and filetype completion for user commands. (Christian Brabandt)
Bram Moolenaar <bram@vim.org>
parents:
2420
diff
changeset
|
1539 -complete=filetype filetype names |'filetype'| |
| 7 | 1540 -complete=function function name |
| 1541 -complete=help help subjects | |
| 1542 -complete=highlight highlight groups | |
| 3503 | 1543 -complete=history :history suboptions |
| 2970 | 1544 -complete=locale locale names (as output of locale -a) |
|
11995
7df3dd3c0ac1
patch 8.0.0878: no completion for :mapclear
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
1545 -complete=mapclear buffer argument |
| 7 | 1546 -complete=mapping mapping name |
| 1547 -complete=menu menus | |
|
10275
6d8b2da002e9
commit https://github.com/vim/vim/commit/9e507ca8a3e1535e62de4bd86374b0fcd18ef5b8
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
1548 -complete=messages |:messages| suboptions |
| 7 | 1549 -complete=option options |
|
9464
be72f4201a1d
commit https://github.com/vim/vim/commit/063b9d15abea041a5bfff3ffc4e219e26fd1d4fa
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1550 -complete=packadd optional package |pack-add| names |
|
2444
3fbd9bce03f1
Support syntax and filetype completion for user commands. (Christian Brabandt)
Bram Moolenaar <bram@vim.org>
parents:
2420
diff
changeset
|
1551 -complete=shellcmd Shell command |
| 2596 | 1552 -complete=sign |:sign| suboptions |
|
2444
3fbd9bce03f1
Support syntax and filetype completion for user commands. (Christian Brabandt)
Bram Moolenaar <bram@vim.org>
parents:
2420
diff
changeset
|
1553 -complete=syntax syntax file names |'syntax'| |
|
4803
220bdea4f579
updated for version 7.3.1148
Bram Moolenaar <bram@vim.org>
parents:
4358
diff
changeset
|
1554 -complete=syntime |:syntime| suboptions |
| 7 | 1555 -complete=tag tags |
| 1556 -complete=tag_listfiles tags, file names are shown when CTRL-D is hit | |
| 3744 | 1557 -complete=user user names |
| 7 | 1558 -complete=var user variables |
| 1559 -complete=custom,{func} custom completion, defined via {func} | |
| 406 | 1560 -complete=customlist,{func} custom completion, defined via {func} |
| 7 | 1561 |
| 27321 | 1562 If you specify completion while there is nothing to complete (-nargs=0, the |
| 1563 default) then you get error *E1208* . | |
| 6259 | 1564 Note: That some completion methods might expand environment variables. |
| 1565 | |
| 557 | 1566 |
|
15125
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1567 Custom completion ~ |
|
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1568 *:command-completion-custom* |
|
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1569 *:command-completion-customlist* *E467* *E468* |
| 7 | 1570 It is possible to define customized completion schemes via the "custom,{func}" |
| 406 | 1571 or the "customlist,{func}" completion argument. The {func} part should be a |
| 1619 | 1572 function with the following signature: > |
| 7 | 1573 |
| 1574 :function {func}(ArgLead, CmdLine, CursorPos) | |
| 1575 | |
| 406 | 1576 The function need not use all these arguments. The function should provide the |
| 1577 completion candidates as the return value. | |
| 1578 | |
| 1579 For the "custom" argument, the function should return the completion | |
| 1580 candidates one per line in a newline separated string. | |
| 1581 | |
| 1582 For the "customlist" argument, the function should return the completion | |
| 557 | 1583 candidates as a Vim List. Non-string items in the list are ignored. |
| 406 | 1584 |
| 1585 The function arguments are: | |
| 7 | 1586 ArgLead the leading portion of the argument currently being |
| 1587 completed on | |
| 1588 CmdLine the entire command line | |
| 557 | 1589 CursorPos the cursor position in it (byte index) |
| 406 | 1590 The function may use these for determining context. For the "custom" |
| 1591 argument, it is not necessary to filter candidates against the (implicit | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
1592 pattern in) ArgLead. Vim will filter the candidates with its regexp engine |
| 28010 | 1593 after function return, and this is probably more efficient in most cases. If |
| 1594 'wildoptions' contains "fuzzy", then the candidates will be filtered using | |
| 1595 |fuzzy-matching|. For the "customlist" argument, Vim will not | |
| 1596 filter the returned completion candidates and the user supplied function | |
| 1597 should filter the candidates. | |
| 7 | 1598 |
| 1599 The following example lists user names to a Finger command > | |
| 1600 :com -complete=custom,ListUsers -nargs=1 Finger !finger <args> | |
| 1601 :fun ListUsers(A,L,P) | |
| 1602 : return system("cut -d: -f1 /etc/passwd") | |
| 1603 :endfun | |
| 1604 | |
| 406 | 1605 The following example completes filenames from the directories specified in |
| 1606 the 'path' option: > | |
| 1607 :com -nargs=1 -bang -complete=customlist,EditFileComplete | |
| 1608 \ EditFile edit<bang> <args> | |
| 1609 :fun EditFileComplete(A,L,P) | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
1610 : return split(globpath(&path, a:A), "\n") |
| 406 | 1611 :endfun |
| 1612 < | |
|
2420
6de9efd58dc0
Updated runtime files. New netrw plugin version.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
1613 This example does not work for file names with spaces! |
|
6de9efd58dc0
Updated runtime files. New netrw plugin version.
Bram Moolenaar <bram@vim.org>
parents:
2413
diff
changeset
|
1614 |
| 557 | 1615 |
|
15125
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1616 Range handling ~ |
|
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1617 *E177* *E178* *:command-range* *:command-count* |
| 236 | 1618 By default, user-defined commands do not accept a line number range. However, |
| 7 | 1619 it is possible to specify that the command does take a range (the -range |
| 1620 attribute), or that it takes an arbitrary count value, either in the line | |
| 1621 number position (-range=N, like the |:split| command) or as a "count" | |
| 1132 | 1622 argument (-count=N, like the |:Next| command). The count will then be |
| 1623 available in the argument with |<count>|. | |
| 1624 | |
| 1625 Possible attributes are: | |
| 7 | 1626 |
| 1627 -range Range allowed, default is current line | |
| 1628 -range=% Range allowed, default is whole file (1,$) | |
| 1629 -range=N A count (default N) which is specified in the line | |
| 2788 | 1630 number position (like |:split|); allows for zero line |
| 1631 number. | |
| 7 | 1632 -count=N A count (default N) which is specified either in the line |
| 171 | 1633 number position, or as an initial argument (like |:Next|). |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1634 -count acts like -count=0 |
| 7 | 1635 |
| 1636 Note that -range=N and -count=N are mutually exclusive - only one should be | |
| 1637 specified. | |
| 1638 | |
|
8951
0bdeaf7092bc
commit https://github.com/vim/vim/commit/aa3b15dbebf333282503d6031e2f9ba6ee4398ed
Christian Brabandt <cb@256bit.org>
parents:
7597
diff
changeset
|
1639 *:command-addr* |
| 6424 | 1640 It is possible that the special characters in the range like ., $ or % which |
| 1641 by default correspond to the current line, last line and the whole buffer, | |
| 1642 relate to arguments, (loaded) buffers, windows or tab pages. | |
| 1643 | |
|
16399
47d6e874955c
patch 8.1.1204: output of :command with address completion is not nice
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1644 Possible values are (second column is the short name used in listing): |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1645 -addr=lines Range of lines (this is the default for -range) |
|
16399
47d6e874955c
patch 8.1.1204: output of :command with address completion is not nice
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1646 -addr=arguments arg Range for arguments |
|
47d6e874955c
patch 8.1.1204: output of :command with address completion is not nice
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1647 -addr=buffers buf Range for buffers (also not loaded buffers) |
|
47d6e874955c
patch 8.1.1204: output of :command with address completion is not nice
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1648 -addr=loaded_buffers load Range for loaded buffers |
|
47d6e874955c
patch 8.1.1204: output of :command with address completion is not nice
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1649 -addr=windows win Range for windows |
|
47d6e874955c
patch 8.1.1204: output of :command with address completion is not nice
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1650 -addr=tabs tab Range for tab pages |
|
47d6e874955c
patch 8.1.1204: output of :command with address completion is not nice
Bram Moolenaar <Bram@vim.org>
parents:
15194
diff
changeset
|
1651 -addr=quickfix qf Range for quickfix entries |
|
16553
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1652 -addr=other ? other kind of range; can use ".", "$" and "%" |
|
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1653 as with "lines" (this is the default for |
|
0e473e9e70c2
patch 8.1.1280: remarks about functionality not in Vi clutters the help
Bram Moolenaar <Bram@vim.org>
parents:
16399
diff
changeset
|
1654 -count) |
| 6424 | 1655 |
|
15125
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1656 |
|
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1657 Special cases ~ |
|
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1658 *:command-bang* *:command-bar* |
| 1132 | 1659 *:command-register* *:command-buffer* |
| 26148 | 1660 *:command-keepscript* |
| 7 | 1661 There are some special cases as well: |
| 1662 | |
| 1663 -bang The command can take a ! modifier (like :q or :w) | |
| 1664 -bar The command can be followed by a "|" and another command. | |
| 1665 A "|" inside the command argument is not allowed then. | |
| 1666 Also checks for a " to start a comment. | |
| 1667 -register The first argument to the command can be an optional | |
| 1668 register name (like :del, :put, :yank). | |
| 1669 -buffer The command will only be available in the current buffer. | |
|
26103
d079ab2ba260
patch 8.2.3584: "verbose set efm" reports location of the :compiler command
Bram Moolenaar <Bram@vim.org>
parents:
26050
diff
changeset
|
1670 -keepscript Do not use the location of where the user command was |
|
d079ab2ba260
patch 8.2.3584: "verbose set efm" reports location of the :compiler command
Bram Moolenaar <Bram@vim.org>
parents:
26050
diff
changeset
|
1671 defined for verbose messages, use the location of where |
|
d079ab2ba260
patch 8.2.3584: "verbose set efm" reports location of the :compiler command
Bram Moolenaar <Bram@vim.org>
parents:
26050
diff
changeset
|
1672 the user command was invoked. |
| 7 | 1673 |
| 1674 In the cases of the -count and -register attributes, if the optional argument | |
| 1675 is supplied, it is removed from the argument list and is available to the | |
| 1676 replacement text separately. | |
| 5340 | 1677 Note that these arguments can be abbreviated, but that is a deprecated |
| 1678 feature. Use the full name for new scripts. | |
| 7 | 1679 |
|
15125
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1680 |
|
b101b193d5ff
patch 8.1.0573: cannot redefine user command without ! in same script
Bram Moolenaar <Bram@vim.org>
parents:
14864
diff
changeset
|
1681 Replacement text ~ |
|
25463
05f9e8f2016c
patch 8.2.3268: cannot use a block with :autocmd like with :command
Bram Moolenaar <Bram@vim.org>
parents:
25402
diff
changeset
|
1682 *:command-repl* |
|
25382
b80e4e9c4988
patch 8.2.3228: cannot use a simple block for the :command argument
Bram Moolenaar <Bram@vim.org>
parents:
24636
diff
changeset
|
1683 The {repl} argument is normally one long string, possibly with "|" separated |
|
b80e4e9c4988
patch 8.2.3228: cannot use a simple block for the :command argument
Bram Moolenaar <Bram@vim.org>
parents:
24636
diff
changeset
|
1684 commands. A special case is when the argument is "{", then the following |
|
b80e4e9c4988
patch 8.2.3228: cannot use a simple block for the :command argument
Bram Moolenaar <Bram@vim.org>
parents:
24636
diff
changeset
|
1685 lines, up to a line starting with "}" are used and |Vim9| syntax applies. |
|
b80e4e9c4988
patch 8.2.3228: cannot use a simple block for the :command argument
Bram Moolenaar <Bram@vim.org>
parents:
24636
diff
changeset
|
1686 Example: > |
|
b80e4e9c4988
patch 8.2.3228: cannot use a simple block for the :command argument
Bram Moolenaar <Bram@vim.org>
parents:
24636
diff
changeset
|
1687 :command MyCommand { |
|
b80e4e9c4988
patch 8.2.3228: cannot use a simple block for the :command argument
Bram Moolenaar <Bram@vim.org>
parents:
24636
diff
changeset
|
1688 echo 'hello' |
|
b80e4e9c4988
patch 8.2.3228: cannot use a simple block for the :command argument
Bram Moolenaar <Bram@vim.org>
parents:
24636
diff
changeset
|
1689 g:calledMyCommand = true |
|
b80e4e9c4988
patch 8.2.3228: cannot use a simple block for the :command argument
Bram Moolenaar <Bram@vim.org>
parents:
24636
diff
changeset
|
1690 } |
|
25521
2063b858cad9
patch 8.2.3297: cannot use all commands inside a {} block
Bram Moolenaar <Bram@vim.org>
parents:
25463
diff
changeset
|
1691 < *E1231* |
|
2063b858cad9
patch 8.2.3297: cannot use all commands inside a {} block
Bram Moolenaar <Bram@vim.org>
parents:
25463
diff
changeset
|
1692 There must be white space before the "{". No nesting is supported, inline |
|
2063b858cad9
patch 8.2.3297: cannot use all commands inside a {} block
Bram Moolenaar <Bram@vim.org>
parents:
25463
diff
changeset
|
1693 functions cannot be used. Commands where a "|" may appear in the argument, |
|
2063b858cad9
patch 8.2.3297: cannot use all commands inside a {} block
Bram Moolenaar <Bram@vim.org>
parents:
25463
diff
changeset
|
1694 such as commands with an expression argument, cannot be followed by a "|" and |
|
2063b858cad9
patch 8.2.3297: cannot use all commands inside a {} block
Bram Moolenaar <Bram@vim.org>
parents:
25463
diff
changeset
|
1695 another command. |
|
25382
b80e4e9c4988
patch 8.2.3228: cannot use a simple block for the :command argument
Bram Moolenaar <Bram@vim.org>
parents:
24636
diff
changeset
|
1696 |
| 23164 | 1697 The replacement text {repl} for a user defined command is scanned for special |
| 1698 escape sequences, using <...> notation. Escape sequences are replaced with | |
| 1699 values from the entered command line, and all other text is copied unchanged. | |
| 1700 The resulting string is executed as an Ex command. To avoid the replacement | |
| 1701 use <lt> in place of the initial <. Thus to include "<bang>" literally use | |
| 788 | 1702 "<lt>bang>". |
| 7 | 1703 |
| 1704 The valid escape sequences are | |
| 1705 | |
| 1706 *<line1>* | |
| 1707 <line1> The starting line of the command range. | |
| 1708 *<line2>* | |
| 1709 <line2> The final line of the command range. | |
|
12419
d216d9e8ac57
patch 8.0.1089: cannot get range count in user command
Christian Brabandt <cb@256bit.org>
parents:
11995
diff
changeset
|
1710 *<range>* |
|
d216d9e8ac57
patch 8.0.1089: cannot get range count in user command
Christian Brabandt <cb@256bit.org>
parents:
11995
diff
changeset
|
1711 <range> The number of items in the command range: 0, 1 or 2 |
| 7 | 1712 *<count>* |
| 1713 <count> Any count supplied (as described for the '-range' | |
| 1714 and '-count' attributes). | |
| 1715 *<bang>* | |
| 1716 <bang> (See the '-bang' attribute) Expands to a ! if the | |
| 1717 command was executed with a ! modifier, otherwise | |
| 1718 expands to nothing. | |
| 22328 | 1719 *<mods>* *<q-mods>* *:command-modifiers* |
|
9230
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1720 <mods> The command modifiers, if specified. Otherwise, expands to |
|
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9230
diff
changeset
|
1721 nothing. Supported modifiers are |:aboveleft|, |:belowright|, |
|
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
9230
diff
changeset
|
1722 |:botright|, |:browse|, |:confirm|, |:hide|, |:keepalt|, |
|
9737
35ce559b8553
commit https://github.com/vim/vim/commit/bc8801c9317eb721a2ee91322669f2dd5d136380
Christian Brabandt <cb@256bit.org>
parents:
9464
diff
changeset
|
1723 |:keepjumps|, |:keepmarks|, |:keeppatterns|, |:leftabove|, |
|
29377
48b086982c01
patch 9.0.0031: <cmod> of user command does not have correct verbose value
Bram Moolenaar <Bram@vim.org>
parents:
29314
diff
changeset
|
1724 |:lockmarks|, |:noautocmd|, |:noswapfile| |:rightbelow|, |
|
48b086982c01
patch 9.0.0031: <cmod> of user command does not have correct verbose value
Bram Moolenaar <Bram@vim.org>
parents:
29314
diff
changeset
|
1725 |:sandbox|, |:silent|, |:tab|, |:topleft|, |:unsilent|, |
|
48b086982c01
patch 9.0.0031: <cmod> of user command does not have correct verbose value
Bram Moolenaar <Bram@vim.org>
parents:
29314
diff
changeset
|
1726 |:verbose|, and |:vertical|. |
|
48b086982c01
patch 9.0.0031: <cmod> of user command does not have correct verbose value
Bram Moolenaar <Bram@vim.org>
parents:
29314
diff
changeset
|
1727 Note that |:filter| is not supported. |
|
9230
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1728 Examples: > |
|
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1729 command! -nargs=+ -complete=file MyEdit |
|
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1730 \ for f in expand(<q-args>, 0, 1) | |
| 27903 | 1731 \ exe '<mods> split ' .. f | |
|
9230
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1732 \ endfor |
|
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1733 |
|
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1734 function! SpecialEdit(files, mods) |
|
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1735 for f in expand(a:files, 0, 1) |
| 27903 | 1736 exe a:mods .. ' split ' .. f |
|
9230
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1737 endfor |
|
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1738 endfunction |
|
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1739 command! -nargs=+ -complete=file Sedit |
|
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1740 \ call SpecialEdit(<q-args>, <q-mods>) |
|
f7fb117883ba
commit https://github.com/vim/vim/commit/63a60ded3fd584847a05dccf058026e682abad90
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1741 < |
| 7 | 1742 *<reg>* *<register>* |
| 1743 <reg> (See the '-register' attribute) The optional register, | |
| 236 | 1744 if specified. Otherwise, expands to nothing. <register> |
| 7 | 1745 is a synonym for this. |
| 1746 *<args>* | |
| 1747 <args> The command arguments, exactly as supplied (but as | |
| 1748 noted above, any count or register can consume some | |
| 1749 of the arguments, which are then not part of <args>). | |
| 1750 <lt> A single '<' (Less-Than) character. This is needed if you | |
| 1751 want to get a literal copy of one of these escape sequences | |
| 1752 into the expansion - for example, to get <bang>, use | |
| 1753 <lt>bang>. | |
| 1754 | |
| 1755 *<q-args>* | |
| 1756 If the first two characters of an escape sequence are "q-" (for example, | |
| 1757 <q-args>) then the value is quoted in such a way as to make it a valid value | |
| 1758 for use in an expression. This uses the argument as one single value. | |
| 300 | 1759 When there is no argument <q-args> is an empty string. |
| 1088 | 1760 *<f-args>* |
| 7 | 1761 To allow commands to pass their arguments on to a user-defined function, there |
| 236 | 1762 is a special form <f-args> ("function args"). This splits the command |
| 1236 | 1763 arguments at spaces and tabs, quotes each argument individually, and the |
| 7 | 1764 <f-args> sequence is replaced by the comma-separated list of quoted arguments. |
| 856 | 1765 See the Mycmd example below. If no arguments are given <f-args> is removed. |
| 1088 | 1766 To embed whitespace into an argument of <f-args>, prepend a backslash. |
| 1767 <f-args> replaces every pair of backslashes (\\) with one backslash. A | |
| 1768 backslash followed by a character other than white space or a backslash | |
| 1769 remains unmodified. Overview: | |
| 1770 | |
| 1771 command <f-args> ~ | |
| 1772 XX ab 'ab' | |
| 1773 XX a\b 'a\b' | |
| 1774 XX a\ b 'a b' | |
| 1775 XX a\ b 'a ', 'b' | |
| 1776 XX a\\b 'a\b' | |
| 1777 XX a\\ b 'a\', 'b' | |
| 1778 XX a\\\b 'a\\b' | |
| 1779 XX a\\\ b 'a\ b' | |
| 1780 XX a\\\\b 'a\\b' | |
| 1781 XX a\\\\ b 'a\\', 'b' | |
| 7 | 1782 |
| 1783 Examples > | |
| 1784 | |
| 1785 " Delete everything after here to the end | |
| 1786 :com Ddel +,$d | |
| 1787 | |
| 1788 " Rename the current buffer | |
| 1789 :com -nargs=1 -bang -complete=file Ren f <args>|w<bang> | |
| 1790 | |
| 1791 " Replace a range with the contents of a file | |
| 1792 " (Enter this all as one line) | |
| 1793 :com -range -nargs=1 -complete=file | |
| 1794 Replace <line1>-pu_|<line1>,<line2>d|r <args>|<line1>d | |
| 1795 | |
| 1796 " Count the number of lines in the range | |
| 42 | 1797 :com! -range -nargs=0 Lines echo <line2> - <line1> + 1 "lines" |
| 7 | 1798 |
| 1799 " Call a user function (example of <f-args>) | |
| 1800 :com -nargs=* Mycmd call Myfunc(<f-args>) | |
| 1801 | |
| 1802 When executed as: > | |
| 1803 :Mycmd arg1 arg2 | |
| 1804 This will invoke: > | |
| 1805 :call Myfunc("arg1","arg2") | |
| 1806 | |
| 1807 :" A more substantial example | |
| 1808 :function Allargs(command) | |
| 1619 | 1809 : let i = 0 |
| 1810 : while i < argc() | |
| 1811 : if filereadable(argv(i)) | |
| 27903 | 1812 : execute "e " .. argv(i) |
| 7 | 1813 : execute a:command |
| 1814 : endif | |
| 1815 : let i = i + 1 | |
| 1816 : endwhile | |
| 1817 :endfunction | |
| 1818 :command -nargs=+ -complete=command Allargs call Allargs(<q-args>) | |
| 1819 | |
| 1820 The command Allargs takes any Vim command(s) as argument and executes it on all | |
| 1821 files in the argument list. Usage example (note use of the "e" flag to ignore | |
| 1822 errors and the "update" command to write modified buffers): > | |
| 1823 :Allargs %s/foo/bar/ge|update | |
| 1824 This will invoke: > | |
| 1825 :call Allargs("%s/foo/bar/ge|update") | |
| 1826 < | |
| 23164 | 1827 If the command is defined in Vim9 script (a script that starts with |
| 1828 `:vim9script` and in a `:def` function) then {repl} will be executed as in Vim9 | |
| 1829 script. Thus this depends on where the command is defined, not where it is | |
| 1830 used. | |
| 1831 | |
|
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1969
diff
changeset
|
1832 When defining a user command in a script, it will be able to call functions |
| 7 | 1833 local to the script and use mappings local to the script. When the user |
| 1834 invokes the user command, it will run in the context of the script it was | |
| 1835 defined in. This matters if |<SID>| is used in a command. | |
| 1836 | |
| 14421 | 1837 vim:tw=78:ts=8:noet:ft=help:norl: |