aboutsummaryrefslogtreecommitdiff
path: root/templates
AgeCommit message (Collapse)Author
2017-06-04Better python supportJosé Luis Lafuente
Use color base0E for keywords.
2017-05-08Fixed color orderMax Christian Pohle
The order in which the colors are getting set seems to play a role. From :h cterm-colors: < When setting the "ctermbg" color for the Normal group, the 'background' option will be adjusted automatically. This causes the highlight groups that depend on 'background' to change! This means you should set the colors for Normal first, before setting other colors. In my case I had base16-tomorrow installed with airline and the whitespace warning of airline was hard to read. It turned out that this was the root cause for that: I had :set background=light before :colorscheme base16-tomorrow in my vimrc and :verbose set background? revealed, that base16-tomorrow.vim had reset it back to dark, even though it does not contain any set background-command.
2017-03-12Don't set guifg for MatchParenThayne McCombs
2017-01-21Fixes :terminal colors in Neovim.Ivan Deschenaux
2017-01-18Add support for pangloss/vim-javascriptGetkey
Fixes #109
2017-01-12Fixes brace colors (#131)Vlad Aituganov
2016-12-28Brightens color for CursorLineNrChris Kempson
2016-12-19Fix Search and IncSearch highlighting (#113)Chris Poliquin
2016-10-27Add fugitive supportJosé Luis Lafuente
2016-10-23Remove ruby interpolation highlighting overrideAaron Williamson
2016-07-09Removed &background setting as it seems to be deprecated.DLWood1001
2016-06-29Darkens the search text two shadesChris Kempson
2016-06-28Updates colorsChris Kempson
2016-06-25Restructured for multiple template file supportChris Kempson