summaryrefslogtreecommitdiffstats
path: root/runtime/doc/options.txt
diff options
context:
space:
mode:
authorChristian Brabandt <cb@256bit.org>2023-11-08 21:23:29 +0100
committerChristian Brabandt <cb@256bit.org>2023-11-08 21:23:29 +0100
commit6a650bf696f1df3214b3d788947447c5bbf1a77d (patch)
tree8734a25b02ca08bc77c0e77694564ed1e0d3e43e /runtime/doc/options.txt
parent1fc47c2c9bf3121268ebab03a0662e0cf2e5cb26 (diff)
patch 9.0.2095: statusline may look different than expectedv9.0.2095
Problem: statusline may look different than expected Solution: do not check for highlighting of stl and stlnc characters statusline fillchar may be different than expected If the highlighting group for the statusline for the current window |hl-StatusLine| or the non-current window |hl-StatusLineNC| are cleared (or do not differ from each other), than Vim will use the hard-coded fallback values '^' (for the non-current windows) or '=' (for the current window). I believe this was done, to make sure the statusline will always be visible and be distinguishable from the rest of the window. However, this may be unexpected, if a user explicitly defined those fillchar characters just to notice that those values are then not used by Vim. So, let's assume users know what they are doing and just always return the configured stl and stlnc values. And if they want the statusline to be non-distinguishable from the rest of the window space, so be it. It is their responsibility and Vim shall not know better what to use. fixes: #13366 closes: #13488 Signed-off-by: Christian Brabandt <cb@256bit.org>
Diffstat (limited to 'runtime/doc/options.txt')
-rw-r--r--runtime/doc/options.txt16
1 files changed, 6 insertions, 10 deletions
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 8f57ac0f0d..be59b69a30 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -1,4 +1,4 @@
-*options.txt* For Vim version 9.0. Last change: 2023 Oct 23
+*options.txt* For Vim version 9.0. Last change: 2023 Nov 06
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -3494,8 +3494,8 @@ A jump table for the options with a short description can be found at |Q_op|.
and the value of that item:
item name default Used for ~
- stl ' ' or '^' statusline of the current window
- stlnc ' ' or '=' statusline of the non-current windows
+ stl ' ' statusline of the current window
+ stlnc ' ' statusline of the non-current windows
vert '|' vertical separators |:vsplit|
fold '-' filling 'foldtext'
foldopen '-' mark the beginning of a fold
@@ -3505,15 +3505,11 @@ A jump table for the options with a short description can be found at |Q_op|.
eob '~' empty lines below the end of a buffer
lastline '@' 'display' contains lastline/truncate
- Any one that is omitted will fall back to the default. For "stl" and
- "stlnc" the space will be used when there is highlighting, '^' or '='
- otherwise.
+ Any one that is omitted will fall back to the default.
Example: >
- :set fillchars=stl:^,stlnc:=,vert:\|,fold:-,diff:-
-< This is similar to the default, except that these characters will also
- be used when there is highlighting.
-
+ :set fillchars=stl:\ ,stlnc:\ ,vert:\|,fold:-,diff:-
+<
For the "stl", "stlnc", "foldopen", "foldclose" and "foldsep" items
single-byte and multibyte characters are supported. But double-width
characters are not supported.