Mercurial > vim
diff runtime/doc/autocmd.txt @ 13037:6e81a68d63a1 v8.0.1394
patch 8.0.1394: cannot intercept a yank command
commit https://github.com/vim/vim/commit/7e1652c63c96585b9e2235c195a3c322b1f11595
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Dec 16 18:27:02 2017 +0100
patch 8.0.1394: cannot intercept a yank command
Problem: Cannot intercept a yank command.
Solution: Add the TextYankPost autocommand event. (Philippe Vaucher et al.,
closes #2333)
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Sat, 16 Dec 2017 18:30:05 +0100 |
| parents | 65d7fd8381a3 |
| children | a6d3e2081544 |
line wrap: on
line diff
--- a/runtime/doc/autocmd.txt +++ b/runtime/doc/autocmd.txt @@ -330,6 +330,7 @@ Name triggered by ~ |TextChanged| after a change was made to the text in Normal mode |TextChangedI| after a change was made to the text in Insert mode +|TextYankPost| after text is yanked or deleted |ColorScheme| after loading a color scheme @@ -956,6 +957,26 @@ TextChangedI After a change was made t current buffer in Insert mode. Not triggered when the popup menu is visible. Otherwise the same as TextChanged. + |TextYankPost| +TextYankPost After text has been yanked or deleted in the + current buffer. The following values of + |v:event| can be used to determine the operation + that triggered this autocmd: + operator The operation performed. + regcontents Text that was stored in the + register, as a list of lines, + like with: > + getreg(r, 1, 1) +< regname Name of the |register| or + empty string for the unnamed + register. + regtype Type of the register, see + |getregtype()|. + Not triggered when |quote_| is used nor when + called recursively. + It is not allowed to change the buffer text, + see |textlock|. + *User* User Never executed automatically. To be used for autocommands that are only executed with