-
-
Notifications
You must be signed in to change notification settings - Fork 9
C syntax highlighting not working as before #34
Comments
Yeah something is strange, i tested some things now and if I try to add for example "local" variables to the I will investigate some more, or maybe @roflcopter4 have an answer for this strangeness? |
I have to admit that I haven't even looked at the code in a few months, I've been writing what is basically a version of this plugin entirely in C (why? because I'm a masochist). Obvious plug here, but if neotags is semi-broken at the moment it might be worth looking at. Right now it is faster and does more than neotags (like actually parsing headers for relevant tags, reading .json files, running things in parallel, and directly talking to neovim without an api in between). Anyway, if you're interested (and don't mind the occasional segfault) it's here. ENDPLUG Otherwise I suppose I really ought to take a look at this problem. I can't really imagine why default highlighting groups would be getting clobbered. As to the customizing problems, I'll take a look too. The way the code worked required ctags to be run with particular arguments and was picky about the order. Adding to the |
I think I have at least partially solved this problem (by throwing away 75% of the code and rewriting it...). Since the rewrite doesn't implement everything yet (C code is 100% broken, some features are ignored, gzip only, etc) I am keeping it in the dev branch, but everything seems to work as it should. If anyone wants to test it that would be helpful. |
FWIW, and if you land here googling the " Plug 'c0r73x/neotags.nvim', { 'branch': 'dev', 'do': ':UpdateRemotePlugins' } Thank you @roflcopter4 ! |
After some time I updated all my plugins in neovim and I found that some of the highlights are not working like cType and others
I'm using rakr/vim-one as my colour scheme I don't see any strange change there.
Anyone can point to me what to look for? I'm getting a bit crazy here
The text was updated successfully, but these errors were encountered: