Aristotle Pagaltzis

This is far more complex to implement than the current way the plugin works. It may or may not even be possible. (And the “a bit more complicated” part is...

It’s far from impossible but it’s a much bigger job than what the plugin does currently. Right now, all it does is scan the current line for potential CSS colours,...

This plugin has been unmaintained for years. [Try with my version](/ap/vim-css-color).

Hey, this version of the plugin hasn’t had any maintenance in a decade. You could try [with my version](/ap/vim-css-color). You didn’t specify whether you mean the accuracy of the colour...

I’ve tried to track this down but I can’t find any sensible reason why it won’t work. By all rights it _should_! Yet it doesn’t. And equally, no change I’ve...

Ah, I found it. The reason was that the matches were being set up without `\>` and vim is satisfied to match just `#bbb` for a match group that includes...

You could just take my fork. It has diverged far from the code @skammer patched and is much faster. He would have to either adopt my code or re-do the...

It’s `Rgb2xterm` that’s slow. I thought about a pre-calculated table for it but unfortunately it would have 24 million entries so the situation would be far worse than now, not...

Any of the 24 million colours may show up in a CSS file so it’s necessary to be able to map any of them down to an xterm colour. But...

Try now. (And sorry for rebasing like a rabid hound.) It should be 5× faster than the original. It still uses the geometric distance scan, but instead of including the...