"Trailing characters" error when opening css files

[bjeanes]

Error detected while processing function <SNR>110_PreviewCSSColorInLine..<SNR>110_MatchColorValue:
line    8:
E488: Trailing characters:  endif¬
Press ENTER or type command to continue

See https://skitch.com/bjeanes/gpdee/2-vim-vim

[ap]

Please provide a minimal example file that triggers the error.

[bjeanes]

a {
  color: #fff;
}

Just that causes those errors in console vim. In MacVim, no errors are displayed, but the colors are not highlighted either.

Here are my other vim plugins and their config: https://github.com/bjeanes/dot-files/blob/master/editors/vim/bundles.vim

[ap]

Hmm. I have added the files from scss-syntax to my .vim and added

autocmd FileType scss syntax cluster sassCssAttributes add=@cssColors

to my .vimrc, but so far I cannot get the after/syntax/css.vim file to get triggered on SCSS files. I tried to spot any other bits I might need in your configuration but I cannot really see anything.

Any idea what is else missing?

[bjeanes]

I was unnecessarily specific in my original issue. This isn't just effecting scss files, but even plain css files. Haven't yet tried sass

[ap]

Then I must suspect a problem of some kind on your end because it works just fine on all of my vim installations and nobody else has reported this either.

What is that “¬” character shown in the error message at the end of the offending line?

[bjeanes]

That char is one of my list char settings:
https://github.com/bjeanes/dot-files/blob/master/editors/vim/ui.vim#L22

The original vim-css-color works (though too slow to use) and this is the
only plugin I've seen these errors with. It's obviously some sort of
interaction between something in this plugin and some other plugin/option
that I have set, but I have no idea how to debug these kinds of things...

[ap]

I wish I could help you but I have no idea how to debug this and no one else seem to be having the problem… so I’m closing this ticket as stalled. If you have figured it please report; or if you have found any other information that might point in the right direction, please reopen.

[ap]

Hey @bjeanes. Can you give d812b6c a spin? It should solve your issue (and be a good bit faster than the old version to boot).

[bjeanes]

Sure thing. I'll try to give it a shot tonight.

[ap]

Any news yet, @bjeanes?

[bjeanes]

Ah sorry... I'm at RailsConf at the moment so haven't really been thinking
about this. I'll try to test soon.

[ap]

@bjeanes: ping? :-)

[bjeanes]

sorry for the delay. I just checked, seems to work fine now!

[ap]

Thanks! I can rest easy closing this then.