base16: do not overwrite StatusLine highlighting

The base16 group contained a reference to the Statusline highlighting
group. That changed highlighting of the group unintentionally and made
the wildmenu unreadable.

Most likely, instead of the 'statusline' group it was meant to use the
airline_c highlighting group. So use this instead.

However there was one additional catch. It used the highlighting from the
vimCommand highlighting group. However that group was only available
when editing vim files, else it would fall back to use the Normal
highlighting group. Since the vimCommand highlighting group however
links to the Statement highlighting group, use that instead. Statement
should always be available.

fixes #158
This commit is contained in:
Christian Brabandt 2018-10-25 08:47:09 +02:00
parent cdbe8d0d61
commit 65217b41da
No known key found for this signature in database
GPG Key ID: F3F92DA383FDDE09

View File

@ -86,9 +86,9 @@ else
let s:N3 = airline#themes#get_highlight('CursorLine')
let g:airline#themes#base16#palette.normal = airline#themes#generate_color_map(s:N1, s:N2, s:N3)
let group = airline#themes#get_highlight('vimCommand')
let group = airline#themes#get_highlight('Statement')
let g:airline#themes#base16#palette.normal_modified = {
\ 'statusline': [ group[0], '', group[2], '', '' ]
\ 'airline_c': [ group[0], '', group[2], '', '' ]
\ }
let s:I1 = airline#themes#get_highlight2(['DiffText', 'bg'], ['DiffAdded', 'fg'], 'bold')