Hi,
Am 19.03.2012 18:44 schrieb "Gautier DI FOLCO" <[email protected]>:
>
> Le 19 mars 2012 10:24, Jürgen Krämer <[email protected]> a écrit :
>
>> You can circumvent those problems by always using both highlight groups.
>> You just have to make sure you return an empty string if the highlight
>> group should not be used for the current modified state:
>>
>> set statusline=%1*\ %f\ %2*%=\
%7*%{&modified?'✖':''}%8*%{&modified?'':'✔'}\ %4*\
<%{&encoding}:%{&fileformat}>\ %5*\ %r%y\ %6*\ %cc,%lL/%LL\ %3p%%
>
> Doesn't work and X/V are vertically cut.
What do you mean with "are vertically cut"? Don't you see the complete
glyphs? This might be because these glyphs might be wider than "normal"
characters in the current font.
How did you set the statusline option? I did set it from my .vimrc and no
autocommand or function was involved.
What happens if you try a shorter example like
set statusline=%f\ %7*%{&modified?'✖':''}%8*%{&modified?'':'✔'}\
%4*%{&encoding}
Regards,
Jürgen
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
