-
Notifications
You must be signed in to change notification settings - Fork 50
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
Attempt to avoid errors on aliased 'contains' #52
base: master
Are you sure you want to change the base?
Conversation
Thanks Neil, this sounds awfully familiar; I must have broken your fix to this very same problem when refactoring for the new syntax_keyword variables. Using |
Ha sorry - it seemed familiar to me too but I managed to convince myself I was imagining it! For some unknown reason 😧 Thanks for taking a look. For reference: guns/vim-clojure-highlight#1 |
👍 |
1 similar comment
👍 |
Any chance of getting this merged? Biting me a little now too. |
Any reason this hasn't been merged yet? |
I believe there was, but I'll have another look. |
Is there any temporary fix that we could do to avoid this issue? I am experiencing the same issue |
Avoid issue described by this PR guns/vim-clojure-static#52 Add forked repository with the fix proposed in the PR. Move vim-polyglot to the end of Plugs to prioritize highlighting that are declared before.
Users with vim-clojure-static and vim-clojure-highlight see errors and broken highlighting when opening some test files. The culprit is
[midje.sweet :refer :all]
as that includes a functioncontains
. And this is illegal in Vim:Similarly a couple of other words (oneline, concealends) will not be recognised; but I'd be very surprised if they turned up in much code!
Note that my example code attached still doesn't highlight 'contains' correctly - for the life of me I can't figure out why as the regular expression generated appears under clojureFunc when I call
:syntax
and pasting that regexp into a manual:syntax match
is fine.