Coffeescript highlighting is broken by a recent commit in this module about vim-css-color

[ap]

That commit adds highlighting of CSS colour references in Javascript strings and comments, so it makes sense that this could be the cause of a change in behaviour.

But Classname isn’t any kind of colour name so it shouldn’t be getting affected.

To debug this can you please place the cursor on each of the words and then run the following command, once with css-color enabled and once disabled? (Meaning 4 results.)

:echo map(synstack(line('.'), col('.')), 'synIDattr(v:val, "name")')

This outputs what syntax highlight groups were matched at the cursor location.

[tremby]

Without vim-css-color, each character in the first line (Classname) is ['coffeeObject']. Each in the second line (CONSTANT) is ['coffeeConstant'].

With vim-css-color, each character of both lines comes up as ['coffeeConstant']. But a word consisting of only a single uppercase character comes up as ['coffeeObject']. (This is the same without vim-css-color.)

[ap]

OK, I guess I have to install the plugin myself and track this down then.

[ap]

Well, adding the W3C colour keywords breaks the highlighting. I’ve not found out why yet.

But I also noticed that the plugin currently doesn’t do much in Coffeescript buffers anyway, because even though they include the Javascript syntax, they mostly use their own syntax groups rather than the Javascript ones – and therefore end up with nothing much highlighted. So I took the cheap way out and just made it stay out of Coffeescript buffers.

I’ll look into adding explicit support for Coffeescript at some other point.

[tremby]

Thanks.