- These two highlight groups are the same by default, should keep
them that way.
- The motivation behind this is to make the scheme more compatible
with the vim-paren-crosshairs plugin
Since I don't use the `fillchars` options (I have no chars separating vertical
splits, I find the bg highlighting to be enough), I set the same bg and fg
colors for the VertSplit group. This commit fixes this by highlighting VertSplit
with the same bg as SignColumn and LineNr and with a slightly lighter fg.
These ideas come from #10 from @wedgwood. Thanks!
Close#9
I thought the foreground color of StatusLine and StatusLineNC impacted the space
in the status line between two vertical splits. I was wrong; that's the
background color.
Before this commit, the status line in an inactive window was "invisible" (same
bg and fg). I made the default status line a little brighter and changed the
fg of the inactive status line so that now it works like it should.
Close#6
- I highlighted the 'Directory' group
- I gave the 'Cursor' group a foreground color because, without one, Normal fg
would be the same as Cursor bg, causing the text to be invisible (only in GUI)
vim
@scottchiefbaker proposed a 256 colors version of Gotham in #1, but I didn't
feel like losing the accuracy of the tailored 16 colors against the portability
and ease of use (no terminal emulator colorscheme needed) of the 256 colors.
This commit adds a gotham-256 version of the colorscheme so that everyone is
able to choose what version to use.
There are a ton of things that could be extracted (maybe into `autoload/`), but
for now I'm leaving this untouched in order to avoid extra boot time when
loading an external file in `autoload/`.
