xenia/home
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Document the current scope and some hooks behaviour

Browse Source
This commit is contained in:
Frank LENORMAND 2016-10-18 15:36:43 +03:00
parent 8b133e32d6
commit f4236fbb8b
2 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/manpages/commands.asciidoc
View File

@ -85,7 +85,9 @@ command *q!* has to be used).
*set* <scope> <name> <value>::
change the value of an option (c.f. the 'options' documentation page),
note that the name of a particular buffer can be specified when the
target *scope* is 'buffer', e.g. set buffer=/path/to/buffer foo "bar"
target *scope* is 'buffer', e.g. set buffer=/path/to/buffer foo "bar";
the scope can also take the `current` special value, which will automatically
point to the narrowest scope available in the current context
*unset* <scope> <name>::
unset the value of an option (c.f. the 'options' documentation page)

9
doc/manpages/hooks.asciidoc
View File

@ -145,9 +145,12 @@ Default hooks
filtering text is the client name
*InsertCompletionShow*::
Triggered when the insert completion menu gets displayed.
Triggered when the insert completion menu gets displayed
*InsertCompletionHide*::
Triggered when the insert completion menu gets hidden.
Triggered when the insert completion menu gets hidden
When not specified, the filtering text is an empty string.
When not specified, the filtering text is an empty string. Note that
some hooks will not consider underlying scopes depending on what context
they are bound to be run into, e.g. the `BufWritePost` hook is a buffer
hook, and will not consider the `window` scope.