Docs: fix formatting and add explanation about "current" scope.
This commit is contained in:
parent
e66073bc94
commit
5ba8293d2b
|
@ -12,8 +12,10 @@ Scopes are named as follows:
|
||||||
|
|
||||||
*window*::
|
*window*::
|
||||||
context linked to the window displaying a buffer
|
context linked to the window displaying a buffer
|
||||||
|
|
||||||
*buffer*::
|
*buffer*::
|
||||||
context linked directly to the buffer
|
context linked directly to the buffer
|
||||||
|
|
||||||
*global*::
|
*global*::
|
||||||
global context linked to the instance of Kakoune
|
global context linked to the instance of Kakoune
|
||||||
|
|
||||||
|
@ -27,6 +29,9 @@ The above priority line implies that objects can have individual values that
|
||||||
will be resolved first in the *window* scope (highest priority), then in
|
will be resolved first in the *window* scope (highest priority), then in
|
||||||
the *buffer* scope, and finally in the *global* scope (lowest priority).
|
the *buffer* scope, and finally in the *global* scope (lowest priority).
|
||||||
|
|
||||||
|
The `set-option` and `unset-option` commands also accept *current* as
|
||||||
|
a valid scope name. It refers to the narrowest scope the option is set in.
|
||||||
|
|
||||||
== Uses
|
== Uses
|
||||||
|
|
||||||
The scope paradigm is very useful as it allows the user to customize the
|
The scope paradigm is very useful as it allows the user to customize the
|
||||||
|
|
Loading…
Reference in New Issue
Block a user