TextYankPost: add information to v:event and update tests

This commit is contained in:
Björn Linse
2016-02-29 15:28:10 +01:00
parent 7ab9ff88e6
commit 2359f6f144
7 changed files with 313 additions and 87 deletions

View File

@@ -308,8 +308,7 @@ Name triggered by ~
|InsertCharPre| when a character was typed in Insert mode, before
inserting it
|TextDeletePost| when some text is deleted (dw, dd, D)
|TextYankPost| when some text is yanked (yw, yd, Y)
|TextYankPost| when some text is yanked or deleted
|TextChanged| after a change was made to the text in Normal mode
|TextChangedI| after a change was made to the text in Insert mode
@@ -725,24 +724,18 @@ InsertCharPre When a character is typed in Insert mode,
It is not allowed to change the text |textlock|.
The event is not triggered when 'paste' is
set.
*TextDeletePost*
TextDeletePost Just after a delete (|d|) command is issued.
Not issued if the black hole register
(|quote_|) is used. The affected text can be
accessed by several ways, through @"
(|quotequote| or |v:register|: >
:echo @"
:echo eval('@' . v:register)
<
*TextYankPost*
TextYankPost Just after a |yank| (|y|) command is issued.
Not issued if the black hole register
(|quote_|) is used. The affected text can be
accessed by several ways, through @"
(|quotequote| or |v:register|: >
:echo @"
:echo eval('@' . v:register)
<
TextYankPost Just after a |yank| or |deleting| command, but not
if the black hole register |quote_| is used nor
for |setreg()|. Pattern must be * because its
meaning may change in the future.
Sets these |v:event| keys:
operator
regcontents
regname
regtype
Recursion is ignored.
It is not allowed to change the text |textlock|.
*InsertEnter*
InsertEnter Just before starting Insert mode. Also for
Replace mode and Virtual Replace mode. The

View File

@@ -1389,7 +1389,19 @@ v:errors Errors found by assert functions, such as |assert_true()|.
*v:event* *event-variable*
v:event Dictionary of event data for the current |autocommand|. The
available keys differ per event type and are specified at the
documentation for each |event|.
documentation for each |event|. The possible keys are:
operator The operation performed. Unlike
|v:operator|, it is set also for an Ex
mode command. For instance, |:yank| is
translated to "|y|".
regcontents Text stored in the register as a
|readfile()|-style list of lines.
regname Requested register (e.g "x" for "xyy)
or the empty string for an unnamed
operation.
regtype Type of register as returned by
|getregtype()|.
*v:exception* *exception-variable*
v:exception The value of the exception most recently caught and not
finished. See also |v:throwpoint| and |throw-variables|.