Comments (3)
@tpope's comment is spot on there.
As things stand currently, the only "clean" way to fix the issue of messed up highlighting after color switching is to avoid overriding the highlighting of syntax files in colorschemes entirely.
I see two ways to encourage colorscheme developers to follow such a policy in templates:
-
Raise a warning every time a highlight group different from the "core" ones is defined;
-
Put a conditional block in the default templates, along these lines:
verbatim if get(g:, '@optionprefix_enable_syntax_hi_groups', 0) " Skip this block by default " Highlight groups for syntax highlighting are defined here endif endverbatim
preceded by a comment explaining why defining syntax highlight groups in a colorscheme is a bad idea. The two are not mutually exclusive, of course.
from vim-colortemplate.
I have added a “Best practices” section to Colortemplate's help file recommending, among the rest, to avoid filetype-specific highlight groups or to define them conditionally.
As far as I can see, this issue not solvable in other ways (except by plugins like colorscheme-switcher—no idea how effective they are, though), not unless something changes in Vim. I will leave this open for the time being, in case someone comes with a better idea.
from vim-colortemplate.
Closing, because this issue has been fixed in Vim (vim/vim#4405).
from vim-colortemplate.
Related Issues (20)
- Variant: 0 HOT 1
- cterm definitions for templates with dark and light backgrounds HOT 5
- Feature request: change meaning of term=/t= and add cterm=/c= HOT 2
- Commit `c7f0542` breaks compilation of vim-solarized8 HOT 3
- New highlight group added: CurSearch HOT 1
- alternative to changing saturation? HOT 3
- Invalid expression error when loading colorscheme HOT 3
- Neovim error for option balloonexpr HOT 3
- :h CTRL-L shadows built-in tag HOT 1
- Handling multiple palettes in a single template for a given background HOT 3
- gitignore tags file? HOT 5
- Verbatim is copied once for every variant HOT 3
- E518: Unknown option: <truncated file path> HOT 5
- Help moving Colortemplate v3 into production HOT 5
- Q: Can you elaborate on the Neovim compatibility directive? And why doesn't it exist in v3? HOT 5
- Not working in Neovim HOT 4
- "Unexpected token" from imported file HOT 1
- Allow color index to be in the range [0, 15] for the 256 variant? (v3) HOT 8
- The `Check` interface seems to disallow scrolling down (v3) HOT 2
- Higlight group definitions with discriminators and without variant restrictions check `has('gui_running')` (v3) HOT 9
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from vim-colortemplate.