Changing `iskeyword` is the wrong fix about vim-css-color

[kien]

Oh, I was just fooling around, editing really old github comments to add markdown markup and change wordings etc, sometimes just to see how the markup looks like. Didn't realise github sends everyone a notification on every update. I'm so sorry! :)

Anyway, regarding this iskeyword fix, I actually use your version now after the last big changes, and with zencoding/ultisnips it doesn't really matter.

[ap]

Hey. Ah. I carried the issue over here because you closed it over there but I lean towards changing this now. You may no longer care, and for me it was never a big issue, but others remain affected.

Now I just have to get around to doing it…

[chelmertz]

I'm not sure if this is the correct ticket but the issue is iskeyword-related:

While editing a .php-file, I try to * when on api on the first line:

$api->help;
$api = 'bla';

but that doesn't find $api on the second line. Can't use the plugin as it is today.

diff --git a/after/syntax/css.vim b/after/syntax/css.vim
index d20bc56..2c2bd86 100644
--- a/after/syntax/css.vim
+++ b/after/syntax/css.vim
@@ -495,7 +495,7 @@ if has("gui_running") || &t_Co==256

   " fix highlighting of "white" in `white-space` etc
   " this really belongs in Vim's own syntax/css.vim ...
-  setlocal iskeyword+=-
+  "setlocal iskeyword+=-

fixes it for me but white-space might be affected (I don't really care, this is too much of a bug to keep around so I've just modified it locally).

[ap]

I just (finally!) fixed this in 9b164ea. I figured it’s really only the white/white-space case where this problem occurs, so a localised one-off fix (which wouldn’t do if there many different problematic cases) should be sufficient.

[chelmertz]

@ap Looks good to me, thank you.