Aristotle Pagaltzis

There is `css_color#disable()` to turn it off in the current buffer, but no way to prevent it from being loaded in a buffer.

Yes, it would be nice. But it’s very difficult to make it work without glitches. And turning on this feature would make it _impossible_ to use regular Vim tabs at...

I don’t know that it’s impossible; it could be that sufficiently clever hackery can make it work, as long as you are willing to give up Vim tabs completely forever....

Yikes. That will be painful at best, if feasible at all. If not, it may instead be possible to highlight the definition (rather than individual uses). I don’t know. I’ll...

That makes sense. I’m not sure disabling is the best choice but there should be some form of explicit support for diff mode should, I agree. (Sorry this fell through...

What is `&syntax` set to at each point?

> ...it starts applying the `jinja` syntax colourization that the modeline was supposed to override, Does it load both the `jinja` and the `css` syntax, or just the `jinja` syntax?...

If you take away the `for` directive to vim-plug when loading CSS Color, does it then work right? I.e. make the line just ````vim Plug 'ap/vim-css-color' ````

Does making that change affect the order of entries you get from `:scriptnames`?

(Basically my understanding is that there are three layers of on-demand loading going on, and their interaction is not working out and my working assumption is that it’s the interaction...