Jay Sitter

Same issue here. Nuking the insert mode mappings doesn't seem to do the trick, as @tpope suggested. Instead, it's [lines 57-58](https://github.com/tpope/vim-rsi/blob/b689ee4276d82feb21b21661a6500755ff6b2fde/plugin/rsi.vim#L57-L58) that seem to be causing the issue for me:...

I would refrain from using polyglot, as not everybody has it installed. Instead, I'd suggest loading up a bunch of filetypes in a `vim --clean` session, then do `:highlight` to...

Because these colors never change, the 8-bit colors that result from those functions shouldn't change, either; they could probably just be hard-coded.

This is now fixed in my active fork (jsit/vim-tomorrow-theme#3)

@tjt263 Check out my active fork at [jsit/vim-tomorrow-theme](/jsit/vim-tomorrow-theme)

I've done my best to merge the two histories into a singe branch on my fork: https://github.com/jsit/vim-tomorrow-theme/commits/master I wonder if it would be best to use vim-tomorrow-theme as the "canonical"...

@jcmuller This repo has been abandoned. Please create a PR at my active fork: [jsit/vim-tomorrow-theme](/jsit/vim-tomorrow-theme)

@chrisbra: @chriskempson has abandoned Tomorrow to focus on Base16, however I have a fork of Tomorrow that incorporates a bunch of improvements and PRs that have been left on this...

@chriskempson Don't the base16 themes require companion terminal themes to be installed?

@chrisbra Is emailing themes to Bram really his preferred method of getting these to him?