Skip to content

Commit 0861af3

Browse files
committed
repeat.txt: Update Vim 8.2.4812
1 parent c585344 commit 0861af3

File tree

1 file changed

+28
-12
lines changed

1 file changed

+28
-12
lines changed

en/repeat.txt

Lines changed: 28 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
*repeat.txt* For Vim version 8.2. Last change: 2022 Jan 21
1+
*repeat.txt* For Vim version 8.2. Last change: 2022 Apr 08
22

33

44
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -210,22 +210,26 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|.
210210

211211
To source a range of lines that doesn't start with the
212212
|:vim9script| command in Vim9 script context, the
213-
|:vim9cmd| modifier can be used.
214-
215-
When a range of lines in a buffer is sourced in the
213+
|:vim9cmd| modifier can be used. If you use a Visual
214+
selection and type ":", the range in the form "'<,'>"
215+
can come before it: >
216+
:'<,'>vim9cmd source
217+
< Otherwise the range goes after the modifier and must
218+
have a colon prefixed, like all Vim9 ranges: >
219+
:vim9cmd :5,9source
220+
221+
< When a range of lines in a buffer is sourced in the
216222
Vim9 script context, the previously defined
217223
script-local variables and functions are not cleared.
218224
This works like the range started with the
219225
":vim9script noclear" command. The "++clear" argument
220226
can be used to clear the script-local variables and
221227
functions before sourcing the script. This works like
222-
the range started with the |:vimscript| command
228+
the range started with the `:vim9script` command
223229
without the "noclear" argument. See |vim9-reload| for
224230
more information.
225231
Examples: >
226-
227232
:4,5source
228-
:vim9cmd :'<,'>source
229233
:10,18source ++clear
230234
231235
*:source!*
@@ -1039,18 +1043,24 @@ For example, to profile the one_script.vim script file: >
10391043
10401044
10411045
:prof[ile] start {fname} *:prof* *:profile* *E750*
1042-
Start profiling, write the output in {fname} upon exit.
1046+
Start profiling, write the output in {fname} upon exit or when
1047+
a `:profile stop` or `:profile dump` command is invoked.
10431048
"~/" and environment variables in {fname} will be expanded.
10441049
If {fname} already exists it will be silently overwritten.
10451050
The variable |v:profiling| is set to one.
10461051

1052+
:prof[ile] stop
1053+
Write the collected profiling information to the logfile and
1054+
stop profiling. You can use the `:profile start` command to
1055+
clear the profiling statistics and start profiling again.
1056+
10471057
:prof[ile] pause
1048-
Don't profile until the following ":profile continue". Can be
1058+
Don't profile until the following `:profile continue`. Can be
10491059
used when doing something that should not be counted (e.g., an
10501060
external command). Does not nest.
10511061

10521062
:prof[ile] continue
1053-
Continue profiling after ":profile pause".
1063+
Continue profiling after `:profile pause`.
10541064

10551065
:prof[ile] func {pattern}
10561066
Profile function that matches the pattern {pattern}.
@@ -1067,11 +1077,17 @@ For example, to profile the one_script.vim script file: >
10671077
after this command. A :profile command in the script itself
10681078
won't work.
10691079

1080+
:prof[ile] dump
1081+
Write the current state of profiling to the logfile
1082+
immediately. After running this command, Vim continues to
1083+
collect the profiling statistics.
10701084

10711085
:profd[el] ... *:profd* *:profdel*
10721086
Stop profiling for the arguments specified. See |:breakdel|
1073-
for the arguments.
1074-
1087+
for the arguments. Examples: >
1088+
profdel func MyFunc
1089+
profdel file MyScript.vim
1090+
profdel here
10751091
10761092
You must always start with a ":profile start fname" command. The resulting
10771093
file is written when Vim exits. For example, to profile one specific

0 commit comments

Comments
 (0)