Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I've been using this config since its beggining. However I wanted to try a few more things regarding Vim and I found out about Vundle (https://github.com/gmarik/vundle)
It is very easy and can handle plugin installation/update/remove in a very nice way.
I was wondering if there is any interesting of using this module with Vundle.
The information found here: http://drupal.org/node/1389448 doesn't seem to work.
Comments
Comment #1
benjifisherI have not tried Vundle. I have been using Pathogen to install vim plugins, and that is what the Drush installation command uses for this project.
There is a recent discussion of Vundle and Pathogen on the vim mailing list, and if you search the archives there are other such discussions. See also this wiki page.
Pathogen is working for me, but I am willing to change if there is a good reason.
Comment #2
bserem CreditAttribution: bserem commentedI got it to work under Vundle by removing most of the "non-drupal" and putting them under git version control in a local repo.
Do you want me to upload it somewhere so you can have a look? Perhaps Vundle would work with a drupal-sandbox. It works fine with local git and github.
If you allow me we could give it a try.
That being said I do not want anyone to switch from Pathogen to something else. However I've had some issues with pathogen, issues that got solved in a few minutes when I switched to
VimVundle.ps: I didn't knew about Vam, thanks
Comment #3
benjifisherI am not sure what permission you are looking for.
I assume you mean Vundle, not Vim.
Comment #4
bserem CreditAttribution: bserem commentedWell, I'm just asking permission to clone your work into a new repo that will be almost the same and will provide no different functionallity in the end.
I know we are under GPL but it is always good to ask :D
Comment #5
bserem CreditAttribution: bserem commentedA Vundle compatible repo with information on how to install is located here:
https://github.com/bserem/vim-drupal
It also available as a drupal sandbox, but because drupal-sandboxes get funky numerical names it isn't such an elegant solution (yet).
I hope it helps and I hope you people like it.
I'm closing this thread but please re-open it if anything related to it occurs :)
Comment #6
benjifisherIt is a little hard to tell, since your initial commit is different from the source, but it looks as though you cloned just the part of this project under bundle/vim-plugin-for-drupal. This has the following effects:
I could not think of a way to get both vim-standard installation and easy drush installation; I chose the latter.
Since you lose the drush commands, I think you break some of the items under the Drupal/Tags menu.
Comment #7
bserem CreditAttribution: bserem commentedI understand, I thought there would be some implications.
I'll document these in the readme. I'll also copy the original README file, it must be within the repo.
Installation with Vundle however works like a charm. Ideally it would be great to clone just the folder I want from the official repo (d.o.->vimrc) but this isn't allowed from what I can tell.
As for automatic drush installation and vimrc file: they helped me a lot when I started with Vim. Your configs were one of the many reason I decided to dig deeper into Vim (thanks btw!). However, after almost 2 years with Vim, I've added some modifications and I created my vimrc file (made it public at https://github.com/bserem/vimfiles you might like it, especially the colors from https://github.com/altercation/vim-colors-solarized)
I believe most Vim users will do that sooner or later, so perhaps an option for an easier standard installation can be of assistance to them.
Because Vundle can automatically install itself it is very easy to install everything typing just
git clone https://github.com/bserem/vimfiles.git && mv vimfiles/.vim* ~
. Vundle will install itself on first run.My point is that on can keep his customized config and add your drupal code into it just by adding one bundle line.
ps: Would you believe it would be better to keep the "simple version" of the plugin in this repo as a different branche? I'll need to check if Vundle can handle branches. There seem to have been some thoughts on it.
Hope all of the above makes sense :)
Comment #8
kostajh CreditAttribution: kostajh commentedJust to say, Vundle installation worked for me based on the instructions provided in this project (the d.o. one, not github).
Comment #9
bserem CreditAttribution: bserem commentedAre you talking about the information provided here: https://drupal.org/node/1389448 ?
Comment #10
kostajh CreditAttribution: kostajh commentedYes:
Bundle 'git://drupalcode.org/project/vimrc.git', {'rtp': 'bundle/vim-plugin-for-drupal/'}
Comment #11
bserem CreditAttribution: bserem commentedHow strange... it seems it was a matter of network problem, because today I can install it this way. Silly me, I should have thought of that the very first date.
I'm digging more into this and I'll change my vim config to use the main repository to do some tests.
Comment #12.0
(not verified) CreditAttribution: commentedadded info on the excisting vundle install guide