New answers tagged

2

I too had encountered a similar problem. In my case, there was a missing (external) executable, leading to an error in Vim on startup, thus preventing lightline from loading correctly. I found that switching windows and opening a new split 'fixed' the issue, ie. adding/moving between splits resulted in lightline updating the statusline correctly. Poking ...


1

A new angle of attack: if has_key(environ(), "MINGW_PREFIX") && has_key(environ(), "GIT_INDEX_FILE") colorscheme default endif Poking around in help environ, it looks like has_key(environ(), <name>) is the recommended way of determining whether a system environment variable is defined. I'm not an expert on what ...


0

You need to set the option laststatus to 2 as explained in the help page of lightline: Problem 4: *lightline-problem-4* Cool statuslines appear only on |:vsp|. Add the following setting to your .vimrc(_vimrc). > set laststatus=2


2

EDIT: user Christian Brabandt points out that v:progpath will still only contain /usr/bin/vim when invoked through git-for-windows, so this solution will not work. Maybe something along these lines? if v:progpath =~ "git" colorscheme default endif The variable v:progpath should contain a path to the running vim executable, and (assuming that ...


2

It is actually the expected behavior, although that is clearly not what was intended. The key is that 'termwinsize' is "local to window", whereas 'buftype' is "local to buffer". There is a slight --- but important --- distinction between "window" and "buffer". :h windows.txt explains this distinction in great detail. ...


Top 50 recent answers are included