Lines Matching refs:that
37 Note that when repeating a command that used a Visual selection, the same SIZE
81 was in that line. For ":v" and ":g!" the command is executed for each not
84 the command. If an error message is given for a line, the command for that
89 range is then not allowed. This is useful to find all lines that match a
97 Make sure that {commands} ends with a whole command, otherwise Vim will wait
139 q Stops recording. (Implementation note: The 'q' that
145 times. Note that register '%' (name of the current
148 The register is executed like a mapping, that means
149 that the difference between 'wildchar' and 'wildcharm'
197 :so[urce] {file} Read Ex commands from {file}. These are commands that
202 that are executed from Normal mode, like you type
266 Note that {name} is the directory name, not the name
283 that the loading order will be reversed, because each
285 Note that for ftdetect scripts to be loaded
312 Note that when using `:packloadall` in the |vimrc|
316 handle that.
351 `:scriptencoding` must be placed after that. E.g.: >
358 Specify the version of Vim for the lines that follow
427 the next characters from that file are read until a <CR> is found. You will
432 nested as deep as the number of files that can be opened at one time (about
443 terminal-independent two character codes. This means that they can be used
451 Win32: Files that are read with ":source" normally have <CR><NL> <EOL>s.
459 Mac Classic: Files that are read with ":source" normally have <CR> <EOL>s.
469 detection, because it's common to start with a line that defines a mapping
470 that ends in a <CR>, which will confuse the automaton.
488 Note however that trailing whitespace in the line before it cannot be
513 Note that when the commands are inside a function, you need to add the 'C'
544 that was a valid continuation line. Using '"\ ' comes closest, even
551 A Vim package is a directory that contains one or more plugins. The
558 - A package can contain multiple plugins that depend on each other.
559 - A package can contain plugins that are automatically loaded on startup and
560 ones that are only loaded when needed with `:packadd`.
592 Note that the files under "pack/foo/opt" are not loaded automatically, only the
599 To load packages earlier, so that 'runtimepath' gets updated: >
604 If the package has an "after" directory, that directory is added to the end of
605 'runtimepath', so that anything there will be loaded later.
636 The extra "!" is so that the plugin isn't loaded if Vim was started with
650 Filetype plugins should go under "pack/*/start", so that they are always
666 This assumes you write one or more plugins that you distribute as a package.
668 If you have two unrelated plugins you would use two packages, so that Vim
695 Here "myfoobar" is a name that the user can choose, the only condition is that
706 generated file in the package means that the user can drop the package in the
715 Suppose you have two plugins that depend on the same functionality. You can
716 put the common functionality in an autoload directory, so that it will be
732 Besides the obvious messages that you can add to your scripts to find out what
751 effect is that Vim will switch the terminal mode before initialisations
769 Comment lines, empty lines and lines that are not executed are skipped. When
788 Commands that require updating the screen should be avoided, because their
796 If you have trouble figuring out where you are, edit the file that defines
817 back to debug mode for the next command that is
822 back to debug mode for the command after the one that
853 When executing a command that is not a specific bytecode instruction but
889 < Note that this only works for commands that are executed when
890 sourcing the file, not for a function defined in that file.
893 Sets a breakpoint, that will break whenever the {expression}
899 variable that does not exist yet. This also means you will
904 valid in the script where it has been defined and if that
906 whenever that particular variable will become visible or
913 {name} is a pattern that is matched with the file or function name. The
933 Note that functions are first loaded and later executed. When they are loaded
984 Profiling means that Vim measures the time that is spent on executing
1008 used when doing something that should not be counted (e.g., an
1015 Profile function that matches the pattern {pattern}.
1019 Profile script file that matches the pattern {pattern}.
1025 Note that profiling only starts when the script is loaded
1064 Lines 7-11 show the time spent in each executed line. Lines that are not
1067 The Count column shows how many times a line was executed. Note that the
1075 mind there are various things that may clobber the results:
1091 - Functions that are deleted before Vim exits will not produce profiling