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

closes: #14062

Signed-off-by: Matt Ellis <m.t.ellis@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>

diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index b70fb15d988f7cf4b9279a495761b1c047d7a53e..48e45e835d334003c14e44ca7730d5ea272fcbec 100644 (file)
--- 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