Mercurial > vim
diff runtime/doc/autocmd.txt @ 20800:e76b83c07bd8 v8.2.0952
patch 8.2.0952: no simple way to interrupt Vim
Commit: https://github.com/vim/vim/commit/be5ee8686a50acf07b823bd293f9c765e533d213
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed Jun 10 20:56:58 2020 +0200
patch 8.2.0952: no simple way to interrupt Vim
Problem: No simple way to interrupt Vim.
Solution: Add the SigUSR1 autocommand, triggered by SIGUSR1. (Jacob Hayes,
closes #1718)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Wed, 10 Jun 2020 21:00:04 +0200 |
| parents | 51bc26d4a393 |
| children | b8ca32dcfabb |
line wrap: on
line diff
--- a/runtime/doc/autocmd.txt +++ b/runtime/doc/autocmd.txt @@ -380,6 +380,7 @@ Name triggered by ~ info |User| to be used in combination with ":doautocmd" +|SigUSR1| after the SIGUSR1 signal has been detected The alphabetical list of autocommand events: *autocmd-events-abc* @@ -1158,6 +1159,7 @@ TextYankPost After text has been yanke It is not allowed to change the buffer text, see |textlock|. {only when compiled with the +eval feature} + *User* User Never executed automatically. To be used for autocommands that are only executed with @@ -1166,6 +1168,15 @@ User Never executed automatically. T used while there are no matching autocommands, you will get an error. If you don't want that, define a dummy autocommand yourself. + + *SigUSR1* +SigUSR1 After the SIGUSR1 signal has been detected. + Could be used if other ways of notifying Vim + are not feasible. E.g. to check for the + result of a build that takes a long time, or + when a motion sensor is triggered. + {only on Unix} + *UserGettingBored* UserGettingBored When the user presses the same key 42 times. Just kidding! :-)