From: Matt Ellis Date: Sat, 24 Feb 2024 16:02:43 +0000 (+0100) Subject: runtime(doc): clarify ':set[l] {option}<' behaviour X-Git-Tag: v9.1.0136~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=374e26aba2e5e0a220b1a7ce1934b0eb5f493e6c;p=thirdparty%2Fvim.git runtime(doc): clarify ':set[l] {option}<' behaviour closes: #14062 Signed-off-by: Matt Ellis Signed-off-by: Christian Brabandt --- diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt index b70fb15d98..48e45e835d 100644 --- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -365,11 +365,24 @@ created, thus they behave slightly differently: For a global option the global value is shown (but that might change in the future). -:setl[ocal] {option}< Set the local value of {option} to its global value by - copying the value. - -:se[t] {option}< For |global-local| options: Remove the local value of - {option}, so that the global value will be used. +:se[t] {option}< Set the effective value of {option} to its global + 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. + +:setl[ocal] {option}< Set the effective value of {option} to its global + 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[lobal][!] ... Like ":set" but set only the global value for a local