Mercurial > vim
annotate runtime/ftplugin/mrxvtrc.vim @ 33732:b140246564f4 v9.0.2095
patch 9.0.2095: statusline may look different than expected
Commit: https://github.com/vim/vim/commit/6a650bf696f1df3214b3d788947447c5bbf1a77d
Author: Christian Brabandt <cb@256bit.org>
Date: Wed Nov 8 21:23:29 2023 +0100
patch 9.0.2095: statusline may look different than expected
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>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Wed, 08 Nov 2023 21:30:04 +0100 |
parents | 2ad54fcf37e3 |
children |
rev | line source |
---|---|
846 | 1 " Created : Wed 26 Apr 2006 01:20:53 AM CDT |
1122 | 2 " Modified : Fri 28 Apr 2006 03:24:01 AM CDT |
846 | 3 " Author : Gautam Iyer <gi1242@users.sourceforge.net> |
4 " Description : ftplugin for mrxvtrc | |
5 | |
6 if exists("b:did_ftplugin") | |
7 finish | |
8 endif | |
9 let b:did_ftplugin = 1 | |
10 | |
11 let b:undo_ftplugin = "setl com< cms< fo<" | |
12 | |
1122 | 13 " Really any line that does not match an option is a comment. But use '!' for |
14 " compatibility with x-defaults files, and "#" (preferred) for compatibility | |
15 " with all other config files. | |
16 " | |
17 " Comments beginning with "#" are preferred because Vim will not flag the | |
18 " first word as a spelling error if it is not capitalised. The '!' used as | |
19 " comment leaders makes Vim think that every comment line is a new sentence. | |
846 | 20 |
1122 | 21 setlocal comments=:!,:# commentstring=#\ %s |
22 setlocal formatoptions-=t formatoptions+=croql |