-
Notifications
You must be signed in to change notification settings - Fork 111
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
Doesn't appear to work with Vundle #25
Comments
Hi @beckyconning. I don't use Vundle myself but it's supposed to be perfectly compatible with Pathogen. I think rather the problem is that you're being overspecific: since the plugin is hosted on github you don't need the full URL. Try the following:
Hope it works and thanks for trying my plugin! |
I'm using vundle it everything seems to work fine here. I had a issue when I first started using it too where I had set json to equal javascript, and it was stopping the plugin from working. You may have something similar setup? |
Sorry, no idea then what's wrong. Hope you figure it out and if you do please share your solution here for future users. |
@elzr switching to the i have other plugins work with a full github url but this one wanted to work like this. i'll do a pull request for the readme file including these instructions and you can decide if you want to include it. thanks again! |
Glad it's working now! :) |
It was working great for me, then I updated and something has broken the loading of the plugin. I last went and looked at the installation of Vundle a few years ago and it seems a lot has changed since then. FWIW, I had to completely wipe my bundle directory and reload the plugins. Now everything works again. |
Yes, I |
Hi, I'm a new vim user so sorry if this is a silly mistake. With Vundle installed I added
to my .vimrc file, wrote the file, reloaded .vimrc with :source, ran :PluginInstall and opened a json file. But I can't see any of the highlighting, warnings or concealing.
Is this something that you could help me fix? Thanks!
The text was updated successfully, but these errors were encountered: