Lines Matching refs:in
26 included in 'cpoptions'. Does not repeat a
69 This is useful if you want to include a '/' in the search pattern or
81 was in that line. For ":v" and ":g!" the command is executed for each not
113 When using "global" in Ex mode, a special case is using ":visual" as a
140 stops recording is not stored in the register, unless
150 applies, and undo might not be synced in the same way.
161 current line). When the last line in the register does
163 the 'e' flag is present in 'cpoptions'.
167 Mappings are not recognized in these commands.
169 at the beginning of a line in a linewise register,
173 Future: Will execute the register for each line in the
177 When '*' is present in 'cpoptions' |cpo-star|, use
178 ":*" in the same way as ":@". This is NOT the default
180 present in 'cpoptions', ":*" is an alias for ":'<,'>",
205 |:bufdo|, in a loop or when another command follows
208 Cannot be used in the |sandbox|.
212 Read Ex commands from {file} in each directory given
220 spaces. Each {file} is searched for in the first
221 directory from 'runtimepath', then in the second
224 in file names, it causes trouble).
232 START search under "start" in 'packpath'
233 OPT search under "opt" in 'packpath'
234 PACK search under "start" and "opt" in
237 under "start" and "opt" in 'packpath'
253 :pa[ckadd][!] {name} Search for an optional plugin directory in 'packpath'
270 below "plugin", just like with plugins in
275 on" command in your .vimrc file), this will also look
281 useful in your .vimrc. The plugins will then be
293 :packl[oadall][!] Load all packages in the "start" directory under each
294 entry in 'packpath'.
297 'runtimepath', then the plugins found in the
312 Note that when using `:packloadall` in the |vimrc|
314 all plugins in 'runtimepath' will be loaded, which
324 Specify the character encoding used in the script.
344 Don't use "ucs-2" or "ucs-4", scripts cannot be in
347 Mark) in utf-8 format Vim will recognize it, no need
350 If you set the 'encoding' option in your |.vimrc|,
359 in the same file. Only applies at the toplevel of
371 Must be the first command in the file.
379 :scr[iptnames] List all sourced script names, in the order they were
392 :fini[sh] Stop sourcing a script. Can only be used in a Vim
398 nested ":try"s in the script. The outermost ":endtry"
401 All commands and command sequences can be repeated by putting them in a named
402 register and then executing it. There are two ways to get the commands in the
405 being executed they are stored in a register. Easy, because you can see
415 An alternative is to put the commands in a file, and execute them with the
425 you ':source' a file with the line "!ls" in it, you will have to type the
426 <Enter> yourself. But if you ':source!' a file with the line ":!ls" in it,
428 not have to type <CR> yourself, unless ":!ls" was the last line in the file.
430 It is possible to put ':source[!]' commands in the script file, so you can
436 of the sourced file, in places where a file name is expected. It will be
438 "other.vimrc" file in the same directory as your ".vimrc" file, you can source
444 in the same way on different kinds of terminals. The first character of a
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.
454 the first line does not end in a <CR>. This fails if the first line has
456 ends in a <CR>, but following ones don't, you will get an error message,
462 the first line does not end in a <CR>. Be careful not to use a file with <NL>
463 linebreaks which has a <CR> in first line.
465 On other systems, Vim expects ":source"ed files to end in a <NL>. These
470 that ends in a <CR>, which will confuse the automaton.
473 Long lines in a ":source"d Ex command script file can be split by inserting
484 are interpreted as if they were given in one line:
487 All leading whitespace characters in the line before a backslash are ignored.
488 Note however that trailing whitespace in the line before it cannot be
502 The backslash is seen as a line-continuation symbol, thus this results in the
524 To add a comment in between the lines start with '"\ '. Notice the space
535 continuation. Using this in Vim would cause incompatibility with Vi.
540 Starting a comment in a continuation line results in all following
553 - A package can be downloaded as an archive and unpacked in its own directory.
565 Let's assume your Vim files are in the "~/.vim" directory and you want to add a
579 When Vim starts up, after processing your .vimrc, it scans all directories in
587 If the "foobar" plugin kicks in and sets the 'filetype' to "some", Vim will
588 find the syntax/some.vim file, because its directory is in 'runtimepath'.
627 This searches for "pack/*/opt/foodebug" in 'packpath' and will find
633 You can also load an optional plugin at startup, by putting this command in
639 It is perfectly normal for a package to only have files in the "opt"
660 The "after" directory is most likely not useful in a package. It's not
702 You could add this packadd command in one of your plugins, to be executed when
706 generated file in the package means that the user can drop the package in the
716 put the common functionality in an autoload directory, so that it will be
755 ":gui" command in the vimrc file.
762 3. Set a breakpoint in a sourced file or user function. You could do this in
765 < This will run Vim and stop in the first line of the "explorer.vim" script.
766 Breakpoints can also be set while in debugging mode.
776 Once in debugging mode, the usual Ex commands can be used. For example, to
782 All commands are executed in the context of the current function or script.
785 are interested in: >
797 the function in another Vim, search for the start of the function and do
838 About the additional commands in debug mode:
854 executed like a normal Ex command, "step" will stop once in the compiled
876 Set a breakpoint in a function. Example: >
882 Set a breakpoint in a sourced file. Example: >
886 Set a breakpoint in the current line of the current file.
890 sourcing the file, not for a function defined in that file.
898 Errors in evaluation are suppressed, you can use the name of a
904 valid in the script where it has been defined and if that
915 if the pattern starts with "^" and ends in "$"). A "*" matches any sequence
916 of characters. 'ignorecase' is not used, but "\c" can be used in the pattern
922 matches "explorer.vim" in the current directory. >
926 matches ".../plugin/explorer.vim" and "explorer.vim" in any other directory.
928 The match for functions is done against the name as it's shown in the output
948 Delete a breakpoint in a function.
951 Delete a breakpoint in a sourced file.
956 When [lnum] is omitted, the first breakpoint in the function or file is
989 the |+reltime| feature, which is present in more builds.
1001 Start profiling, write the output in {fname} upon exit.
1002 "~/" and environment variables in {fname} will be expanded.
1022 defined in it.
1023 When the [!] is added then all functions defined in the script
1026 after this command. A :profile command in the script itself
1050 7 9 0.000096 for i in range(8) ~
1058 the "Total" time reduced by time spent in:
1064 Lines 7-11 show the time spent in each executed line. Lines that are not
1068 "for" command in line 7 is executed one more time as the following lines.
1074 Profiling should give a good indication of where time is spent, but keep in
1079 are displayed in micro seconds.
1085 - If you have several commands in one line you only get one time. Split the
1089 function. There is some overhead in between.
1098 mode kicks in or the processor frequency is reduced to save power.