Great idea. about vim-colortemplate HOT 4 CLOSED

Thanks for your feedback!

Re your first point, I see that the issue can still be reproduced with Solarized8. If I understand correctly, it depends on Solarized defining syntax highlight groups for specific filetypes (e.g., Vim) with, say, hi vimCommand… rather than hi link vimCommand…. I vaguely remember something similar discussed in Vim mailing list, but I don't remember the details. If following some rules can prevent messing with syntax highlighting, I will certainly enforce them (and update Solarized8 accordingly—curious that no one has reported the issue yet).

Re vim-airline support, what would that entail? Isn't it just a matter of defining some custom highlight groups? For things like other plugins's support, I'd be more keen to add customization points for those plugins to hook into rather than hard code something in colortemplate.

from vim-colortemplate.

The thread I had in mind is "syntax reset" in colorschemes from vim-dev, btw.

from vim-colortemplate.

"Re vim-airline support, what would that entail? Isn't it just a matter of defining some custom highlight groups? For things like other plugins's support, I'd be more keen to add customization points for those plugins to hook into rather than hard code something in colortemplate."

It involves creating a separate .vim file in the autoload directory. vim-airline is so popular that you might consider just including it out of the box as part of the template. It wouldn't hurt anyone if airline wasn't installed.

from vim-colortemplate.

Since these are two distinct issues, I have opened #3 and #4. So I am closing this. Feel free to continue the discussion there.

from vim-colortemplate.