Lines Matching refs:be
160 When Vim has read "aa", it will need to get another character to be able to
161 decide if "aa" or "aaa" should be mapped. This means that after typing "aa"
170 "<unique>" can be used in any order. They must appear right after the
175 be effective in the current buffer only. Example: >
182 The "<buffer>" argument can also be used to clear mappings: >
190 When defining a buffer-local mapping for "," there may be a global mapping
193 <nowait> argument. Then the mapping will be used when it matches, Vim does
194 not wait for more characters to be typed. However, if the characters were
204 To define a mapping which will not be echoed on the command line, add
207 The search string will not be echoed when using this mapping. Messages from
211 Prompts will still be given, e.g., for inputdialog().
225 "<SID>". This can be used to avoid that mappings from outside a script
237 When defining a local mapping, there will also be a check if a global map
250 The result of the s:InsertDot() function will be inserted. It could check the
254 defined in can be found.
271 Also, keep in mind that the expression may be evaluated when looking for
281 This can be solved by inserting <Ignore> before the character that is
323 be seen as a special key.
335 preserved, so tricks with |gv| are not needed. Commands can be invoked
355 <Cmd> commands must terminate, that is, they must be followed by <CR> in the
418 :nunmap can also be used outside of a monastery.
456 Operator-pending mappings can be used to define a movement command that can be
462 the omap start Visual mode to select the text to be operated upon. Example
486 Generally: Whenever a character is to be typed that is part of the text in the
491 In Insert mode and in Command-line mode the mappings can be disabled with
498 Language mappings will never be applied to already mapped characters. They
526 (or '|') is considered to be part of {rhs}. This allows the {rhs} to end
532 The |:filter| command can be used to select what mappings to list. The
553 automatically be translated into the internal code and become the second
558 (see table of keys |key-notation|, all keys from <Up> can be used). The
559 first ten function keys can be defined in two ways: Just the number, like
561 refers to function key 10, defined with option 't_f10', which may be
562 function key zero on some keyboards. The <> form cannot be used when
565 termcap entry. Any string entry can be used. For example: >
571 different terminals without modification (the function key will be
573 terminal you are using. The termcap must be correct for this to work, and you
590 also be used like CTRL-V. The <> notation can be fully used then |<>|. But
595 sequence "<Bslash>" can be used. This avoids the need to double backslashes
602 When using the GUI version on MS-Windows CTRL-C can be mapped to allow a Copy
609 If you want a {rhs} that starts with a space, use "<Space>". To be fully Vi
632 two bytes 0xc3 0xa1. You don't want the 0xc3 byte to be mapped then or
633 otherwise it would be impossible to type the á character.
637 "<Leader>" can be used. It is replaced with the string value of "mapleader".
653 instead of "mapleader". <LocalLeader> is to be used for mappings which are
657 In a global plugin <Leader> should be used and in a filetype plugin
658 <LocalLeader>. "mapleader" and "maplocalleader" can be equal. Although, if
665 In a script the special key name "<SID>" can be used to define a mapping
669 The special key name "<Plug>" can be used for an internal mapping, which is
670 not to be matched with any key sequence. This is useful in plugins
675 construct can be used:
685 character is considered to be part of the {lhs} or {rhs}. However, one can
702 When 'b' is present in 'cpoptions', "\|" will be recognized as a mapping
720 and CTRL-X is not mapped. This was done to be able to use all the named
729 otherwise you would not be able to use those commands anymore. Here are a few
734 characters may be used as well. |:map-alt-keys|
742 See the file "index" for keys that are not used and thus can be mapped without
751 the '<' flag must not be present in 'cpoptions' for this to work). >
776 character. This is because Vim cannot know if the next character will be a
779 option). After that it assumes that the 'q' is to be interpreted as such. If
791 When typing \a the buffer-local mapping will be used immediately. Vim will
792 not wait for more characters to see if the user might be typing \abc.
795 There are situations where key codes might not be recognized:
811 < Type the <F1> as four characters. The part after the "=" must be done with
819 Another problem may be that when keeping ALT or Meta pressed the terminal
824 {lhs} is typed, it will be replaced with {rhs}. When the {lhs} which is
825 included in {rhs} is encountered it will be replaced with {rhs}, and so on.
834 {rhs} will not be mapped again.
843 place until the text is found not to be a part of a {lhs}. For example, if
870 rxvt. If your <A-k> mappings don't work it might be that the terminal is
881 On the Linux console, this behavior can be toggled with the "setmetamode"
899 UTF-8 locales. On terminals like xterm, the "metaSendsEscape" resource can be
907 Xterm and a few other terminals can be put in a mode where keys with modifiers
936 after the CTRL-V key. This can be used to check whether modifyOtherKeys is
940 When the 'esckeys' option is off, then modifyOtherKeys will be disabled in
949 specified function will be called.
997 An <expr> mapping is used to be able to fetch any prefixed count and register.
1001 Note that the 'selection' option is temporarily set to "inclusive" to be able
1009 The `mode()` function will return the state as it will be after applying the
1028 stands for. This can be used to save typing for often used long words. And
1049 characters may be of any type, excluding space and tab. {this type
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
1104 the abbreviation to avoid it to be replaced. A CTRL-V in front of a normal
1122 problem. But abbreviations can be mapped. {some versions of Vi support
1128 Just like mappings, abbreviations can be local to a buffer. This is mostly
1210 CTRL-V has to be used to avoid the special meaning of most non printable
1211 characters. How many CTRL-Vs need to be typed depends on how you enter the
1222 and fourth ^Vs, and the ^[, to be entered into the command-line.
1232 to be quoted. (Although quoting isn't harmful; that's why typing 7
1240 abbreviation will be displayed.
1257 this, they can be made local to the script.
1260 The string "<SID>" can be used in a mapping or menu. This requires that the
1268 When defining a function in a script, "s:" can be prepended to the name to
1278 function itself was defined. Also, the "s:var" local script variables can be
1285 In case the value is used in a context where <SID> cannot be correctly
1297 The "<SNR>" will be shown when listing functions and mappings. This is useful
1300 The |:scriptnames| command can be used to see which scripts have been sourced
1310 be completed as filenames or buffer names, etc), except that when the command
1320 They cannot be used for a user defined command. ":Print" is also an existing
1321 command, but it is deprecated and can be overruled.
1323 The other characters of the user command can be uppercase letters, lowercase
1326 be the user command ":Cc2" without an argument, or the command ":Cc" with
1330 When using a user-defined command, the command can be abbreviated. However, if
1331 an abbreviation is not unique, an error will be issued. Furthermore, a
1354 The list can be filtered on command name with
1381 that script will be silently replaced.
1418 -nargs=+ Arguments must be supplied, but any number are allowed
1420 Arguments are considered to be separated by (unescaped) spaces or tabs in this
1435 intended! Calling a function may be an alternative.
1443 completion can be enabled:
1489 or the "customlist,{func}" completion argument. The {func} part should be a
1538 argument (-count=N, like the |:Next| command). The count will then be
1552 Note that -range=N and -count=N are mutually exclusive - only one should be
1580 -bar The command can be followed by a "|" and another command.
1583 -register The first argument to the command can be an optional
1585 -buffer The command will only be available in the current buffer.
1593 Note that these arguments can be abbreviated, but that is a deprecated
1608 There must be white space before the "{". No nesting is supported, inline
1609 functions cannot be used. Commands where a "|" may appear in the argument,
1610 such as commands with an expression argument, cannot be followed by a "|" and
1744 `:vim9script` and in a `:def` function) then {repl} will be executed as in Vim9
1748 When defining a user command in a script, it will be able to call functions