Lines Matching refs:be
29 Simple changes can be repeated with the "." command. Without a count, the
31 last one. |v:count| and |v:count1| will be set.
34 register number will be incremented. See |redo-register| for an example how
102 The previous context mark will only be set once (with "''" you go back to
109 This replaces all occurrences of "pat" with "PAT". The same can be done with:
115 execute commands there until you use |Q| to return to Ex mode. This will be
146 file) and '#' (name of the alternate file) cannot be
150 applies, and undo might not be synced in the same way.
162 not have a <CR> it will be added automatically when
206 the display won't be updated while executing the
208 Cannot be used in the |sandbox|.
219 < There can be multiple {file} arguments, separated by
248 when no file could be found.
269 will be sourced. This allows for using subdirectories
281 useful in your .vimrc. The plugins will then be
283 that the loading order will be reversed, because each
285 Note that for ftdetect scripts to be loaded
301 how this can be useful.
305 can be done earlier.
307 Packages will be loaded only once. Using
314 all plugins in 'runtimepath' will be loaded, which
319 happens to be aborted, further plugins will be loaded.
325 The following lines will be converted from [encoding]
332 can be used to restrict conversion to a sequence of
335 ... lines to be converted ...
341 line can't be converted there is no error and the
344 Don't use "ucs-2" or "ucs-4", scripts cannot be in
351 `:scriptencoding` must be placed after that. E.g.: >
363 version supports E999 will be given. You either need
371 Must be the first command in the file.
388 When the current buffer can't be |abandon|ed and the !
392 :fini[sh] Stop sourcing a script. Can only be used in a Vim
401 All commands and command sequences can be repeated by putting them in a named
412 Often used command sequences can be put under a function key with the ':map'
416 ':source!' command. Useful for long command sequences. Can be combined with
431 make a top-down hierarchy of script files. The ':source' command can be
432 nested as deep as the number of files that can be opened at one time (about
433 15). The ':source!' command can be nested up to 15 levels deep.
436 of the sourced file, in places where a file name is expected. It will be
443 terminal-independent two character codes. This means that they can be used
445 key code is 0x80 or 128, shown on the screen as "~@". The second one can be
446 found in the list |key-notation|. Any of these codes can also be entered
448 the <t_xx> termcap codes, these can only be used in mappings.
453 file made on Unix), this will be recognized if 'fileformats' is not empty and
457 because the <CR> from the first lines will be lost.
461 file made on Unix), this will be recognized if 'fileformats' is not empty and
473 Long lines in a ":source"d Ex command script file can be split by inserting
475 There can be white space before the backslash, which is ignored.
488 Note however that trailing whitespace in the line before it cannot be
493 space at the end of a line is hard to see and may be accidentally deleted. >
541 continuation lines to be part of the comment. Since it was like this
553 - A package can be downloaded as an archive and unpacked in its own directory.
556 - A package can be a git, mercurial, etc. repository. That makes it really
582 See |packload-two-steps| for how these two steps can be useful.
605 'runtimepath', so that anything there will be loaded later.
630 This could be done if some conditions are met. For example, depending on
674 you could use a repository. An archive can be used by more users, but is a
675 bit harder to update to a new version. A repository can usually be kept
676 up-to-date easily, but it requires a program like "git" to be available.
679 Your directory layout would be like this:
702 You could add this packadd command in one of your plugins, to be executed when
716 put the common functionality in an autoload directory, so that it will be
757 2. Run a command with ":debug" prepended. Debugging will only be done while
766 Breakpoints can also be set while in debugging mode.
770 a line contains two commands, separated by "|", each command will be displayed
776 Once in debugging mode, the usual Ex commands can be used. For example, to
788 Commands that require updating the screen should be avoided, because their
789 effect won't be noticed until after leaving debug mode. For example: >
791 won't be very helpful.
800 Additionally, these commands can be used:
805 things might still be executed, doesn't abort
855 context, where local variables can be inspected, and once just before
879 can be set before the function is defined.
914 pattern is like what is used for autocommands. There must be a full match (as
916 of characters. 'ignorecase' is not used, but "\c" can be used in the pattern
958 The {name} must be exactly the same as what was typed for the ":breakadd"
1002 "~/" and environment variables in {fname} will be expanded.
1003 If {fname} already exists it will be silently overwritten.
1007 Don't profile until the following ":profile continue". Can be
1008 used when doing something that should not be counted (e.g., an
1024 will also be profiled.
1078 function. It may only be as accurate as 1/100 second, even though the times