kevin/neovim
1
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2024-12-29 14:41:06 -07:00
Code Issues Packages Projects Releases Wiki Activity

vim-patch:374e26aba2e5 (#27617)

Browse Source 
runtime(doc): clarify ':set[l] {option}<' behaviour

closes: vim/vim#14062

374e26aba2

Co-authored-by: Matt Ellis <m.t.ellis@gmail.com>
This commit is contained in:
zeertzjq 2024-02-25 08:19:43 +08:00 committed by GitHub
parent 091e374c7f
commit 52fe3741aa
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 17 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
runtime/doc/options.txt
View File

@ -302,11 +302,24 @@ created, thus they behave slightly differently:
For a global option the global value is For a global option the global value is
shown (but that might change in the future). shown (but that might change in the future).
:setl[ocal] {option}< Set the local value of {option} to its global value by :se[t] {option}< Set the effective value of {option} to its global
copying the value. value.
For string |global-local| options, the local value is
removed, so that the global value will be used.
For all other options, the global value is copied to
the local value.
:se[t] {option}< For |global-local| options: Remove the local value of :setl[ocal] {option}< Set the effective value of {option} to its global
{option}, so that the global value will be used. value.
For number and boolean |global-local| options, the
local value is removed, so that the global value will
be used.
For all other options, including string |global-local|
options, the global value is copied to the local
value.
Note that the behaviour for |global-local| options is slightly different
between string and number-based options.
*:setg* *:setglobal* *:setg* *:setglobal*
:setg[lobal][!] ... Like ":set" but set only the global value for a local :setg[lobal][!] ... Like ":set" but set only the global value for a local