-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This overides 'iskeyword' for all filetypes. #20
Comments
This is weird, it should affect only css/html/stylus/less/sass filtypes. |
I confirm. Just about now i came up whith this bug. |
I think this is the same issue referred to here: spf13/spf13-vim#547 |
I'm running into the same issue, came here from |
Yeah same problem, i'll probably fork it, delete those rows, UnBundle in spf13 and add my fork. |
Hi all, those rows are fix for this issue The easiest way is to make a backup of isk and revert to it when buffer is not css/sass/less. I will try to fix that. Any pull requests are welcome. |
Using (update: just found pull request #18, which does this) On a separate note, I'd really prefer the full usage of |
Incidentally, I don't think this is a good solution in general. This plugin is also activated for Vim files. Messing with I'd recommend looking for a different solution to #7. Perhaps modifying your regexes to require they follow a |
+1 this is very invasive and was difficult to track down :( |
Yo any news here? |
@gorodinskiy just remove those lines already :) and remove colors for names, it's not so helpful anyway, you know that white is white, and orange is orange, there is no point in highlighting this. it is harder to see rgb or hex colors to see what colors are they. |
@gorodinskiy can you please just accept some of the patches or comment on them? |
Or just remove them from this plugin #25 |
Seconded, I can't use this plugin until this is fixed, it breaks
|
This is an example of why I regret using plugins. You need to document this clearly until fixed otherwise you are wasting a lot of people's time trying to 'fix' their configuration. |
Just discovered that it was this plugin that was doing this to me as well, was driving me insane |
More than 2 years have passed since any code has been committed to this repo so I think it time to consider it dead. |
As an alternative, https://github.com/ap/vim-css-color seems to be maintained. |
Using `set isk` changes rules about what characters count as keywords in buffers that don't contain CSS. Plugins should use `setlocal` for to change settings for a buffer. Updated the command invocation to use `iskeyword` to improve clarity about what the function is doing. Fix gko#20. Fix gko#22. Fix gko#26.
The same issues |
Welcome to 2020. I'm facing this issue if I use this alongside More specifically, " this is only possible on vim version above 7
if v:version >= 700
try
syn include @CSS3 syntax/css/*.vim
catch
endtry
endif The |
At
after/syntax/css/vim-coloresque.vim:125
you will find these rows.This actually overides
iskeyword
in all myfiletypes
and thats not what i expected. Motions and syntax highlighting becomes very different in example ruby and javascript where i expect.
to actually break the word.The text was updated successfully, but these errors were encountered: