Lines Matching refs:that
133 command applies. Note that ":map" and ":map!" are
161 decide if "aa" or "aaa" should be mapped. This means that after typing "aa"
162 that mapping won't get expanded yet, Vim is waiting for another character.
191 that starts with ",". Then you need to type another character for Vim to know
196 Note that this works when the <nowait> mapping fully matches and is found
200 - There is another buffer-local mapping that partly matches, but it is
224 in the {rhs} using mappings that were defined local to a script, starting with
225 "<SID>". This can be used to avoid that mappings from outside a script
230 preferred, because it's clearer that remapping is (mostly) disabled.
248 expression is evaluated to obtain the {rhs} that is used. Example: >
253 namespace. Use <SID> in the RHS so that the script that the mapping was
256 For abbreviations |v:char| is set to the character that was typed to trigger
261 evaluate to an empty string. If something changed that requires Vim to
263 This is similar to "nothing" but makes Vim return from the loop that waits for
271 Also, keep in mind that the expression may be evaluated when looking for
279 You will notice that g:column has the value from before executing "f!",
281 This can be solved by inserting <Ignore> before the character that is
293 that, or use a |<Cmd>| mapping instead.
304 Here is an example that inserts a list number that increases: >
320 empty string, so that nothing is inserted.
322 Note that using 0x80 as a single byte before other text does not work, it will
355 <Cmd> commands must terminate, that is, they must be followed by <CR> in the
421 that quite often "Visual" is mentioned where both Visual and Select mode
456 Operator-pending mappings can be used to define a movement command that can be
463 that operates on a function name in the current line: >
465 The CTRL-U (<C-U>) is used to remove the range that Vim may insert. The
479 ":lmap" defines a mapping that applies to:
483 - the argument of the commands that accept a text character, such as "r" and
486 Generally: Whenever a character is to be typed that is part of the text in the
499 are only used for typed characters. This assumes that the language mapping
521 * indicates that it is not remappable
522 & indicates that only script-local mappings are remappable
549 1. The Vi-compatible method: Map the key code. Often this is a sequence that
551 you have to type CTRL-V before hitting the function key. Note that when
570 The advantage of the second and third method is that the mapping will work on
588 Note that only CTRL-V is mentioned here as a special character for mappings
609 If you want a {rhs} that starts with a space, use "<Space>". To be fully Vi
617 An easier way to get a mapping that doesn't produce anything, is to use
619 For example, to make sure that function key 8 does nothing at all: >
647 Note that the value of "mapleader" is used at the moment the mapping is
648 defined. Changing "mapleader" after that has no effect for already defined
652 <LocalLeader> is just like <Leader>, except that it uses "maplocalleader"
666 that's local to the script. See |<SID>| for details.
707 When you have a mapping that contains an Ex command, you need to put a line
716 Note that when an error is encountered (that causes an error message or beep)
719 Note that the second character (argument) of the commands @zZtTfF[]rm'`"v
728 for the {lhs}. You will have to avoid keys that are used for Vim commands,
732 <S-F2>, etc. Note that <F1> is already used for the help command.
737 - Use a key that is a synonym for another command. For example: CTRL-P and
742 See the file "index" for keys that are not used and thus can be mapped without
779 option). After that it assumes that the 'q' is to be interpreted as such. If
798 - The key code is after character(s) that are mapped. E.g., "<F1><F1>" or
801 The result is that the key code is not recognized in this situation, and the
819 Another problem may be that when keeping ALT or Meta pressed the terminal
827 only problem is that the only way to stop this is by causing an error. The
868 By default Vim assumes that pressing the ALT key sets the 8th bit of a typed
869 character. Most decent terminals can work that way, such as xterm, aterm and
870 rxvt. If your <A-k> mappings don't work it might be that the terminal is
882 command. Bear in mind that not using an ESC prefix could get you in trouble
883 with other programs. You should make sure that bash has the "convert-meta"
886 configuration). For that, you can add the line: >
894 as the first line, if that file exists on your system, to keep global options.
896 Then you should use CTRL-V before that character.
898 Bear in mind that convert-meta has been reported to have troubles when used in
901 on the terminal; that's a good last resource in case you want to send ESC when
927 Note that <C-{> is used and not <C-S-[> or <C-S-{>. This works on most
929 <C-|> instead of <C-S-\> or <C-S-|>. Note that '|' has a special meaning in a
932 WARNING: if you map <C-[> you may very well break any key codes that start
935 A known side effect is that in Insert mode the raw escape sequence is inserted
947 you must create a mapping that first sets the 'operatorfunc' option and then
965 Here is an example that counts the number of spaces with <F4>: >
1001 Note that the 'selection' option is temporarily set to "inclusive" to be able
1005 Also note that the 'clipboard' option is temporarily emptied to avoid
1027 If you enter a word that is an abbreviation, it is replaced with the word it
1054 Examples of strings that cannot be abbreviations: "a.b", "#def", "a b", "_$r"
1057 This can also be the <Esc> that ends insert mode or the <CR> that ends a
1099 that would trigger the abbreviation. E.g. CTRL-V <Space>. Or type part of
1149 :ab[breviate] {lhs} list the abbreviations that start with {lhs}
1151 avoid that a typed {lhs} is expanded, since
1165 with the {rhs}. This is done so that you can even
1227 how it should appear in your .exrc file, if you choose to go that
1232 to be quoted. (Although quoting isn't harmful; that's why typing 7
1255 When using several Vim script files, there is the danger that mappings and
1260 The string "<SID>" can be used in a mapping or menu. This requires that the
1263 key code <SNR>, followed by a number that's unique for the script, and an
1276 defined in. This means that new functions and mappings it defines can also
1282 the script it was defined in. This makes it possible that the command calls a
1310 be completed as filenames or buffer names, etc), except that when the command
1324 letters or digits. When using digits, note that other commands that take a
1343 It is recommended that full names for user-defined commands are used in
1359 :com[mand] {cmd} List the user-defined commands that start with {cmd}
1380 script again, a command that was previously defined in
1381 that script will be silently replaced.
1388 Delete the user-defined command {cmd} that was defined
1410 reported if any are supplied). However, it is possible to specify that the
1424 Note that arguments are used as text, not as expressions. Specifically,
1535 it is possible to specify that the command does take a range (the -range
1536 attribute), or that it takes an arbitrary count value, either in the line
1552 Note that -range=N and -count=N are mutually exclusive - only one should be
1556 It is possible that the special characters in the range like ., $ or % which
1593 Note that these arguments can be abbreviated, but that is a deprecated
1642 Note that these are not yet supported: |:noautocmd|,
1743 If the command is defined in Vim9 script (a script that starts with