Vundle.vim

I had it originally as https://github.com/gmarik/Vundle.vim.git definitely gone, or gone private

It's only a matter of time until someone abuses a publicly editable wiki. For example, as someone noticed on Reddit[1], a link to Git for Windows on Vundle's wiki was replaced with a link to malware: https://github.com/VundleVim/Vundle.vim/wiki/Vundle-for-Windows/_compare/3aeb22ac39229af4312f2be1052ead184dd5b54d...aa3d293dd18ae1cb4f049c43b73b951651515863 In fact, most of the recent edits (made by many different accounts) were malicious: https://github.com/VundleVim/Vundle.vim/wiki/Vundle-for-Windows/_history I recommend restricting editing in your GitHub wikis to collaborators only. [1] - https://www.reddit.com/r/vim/comments/zzcn10/vimorg_autosave_vundle_plugin_windows…

Does anyone know the current state of the Vundle.vim[0] project? It seems that there haven't been any code commits/merges on any of the branches since months....?! Greetz! [0] https://github.com/VundleVim/Vundle.vim

I'm surprised nobody mentioned Vundle: https://github.com/VundleVim/Vundle.vim (13k stars)

package manager: https://github.com/VundleVim/Vundle.vim surround: https://github.com/tpope/vim-surround repeat: http://www.vim.org/scripts/script.php?script_id=2136 git: https://github.com/tpope/vim-fugitive (tim pope plugin) undo: https://github.com/sjl/gundo.vim for repls: https://github.com/jpalardy/vim-slime for html: http://emmet.io/

Reminds me of vim plugin managers like Vundle or NeoBundle. The way they work is you specify a package name and it uses a heuristic to figure out where to look. To steal from the Vundle README... https://github.com/VundleVim/Vundle.vim " The following are examples of different formats supported. " Keep Plugin commands between vundle#begin/end. " plugin on GitHub repo Plugin 'tpope/vim-fugitive' " plugin from http://vim-scripts.org/vim/scripts.html Plugin 'L9' " Git plugin not hosted on GitHub Plugin 'git://git.wincent.com/command-t.git' " git repos on your local machine (i.e. when working on your own plugin) Plugin 'file:///home/gmarik/path/to/plugin' " The sparkup vim script is in a subdirectory of this repo called vim. " Pass the path to set the runtimepath properly. Plugin 'rstacruz/s

See also pathogen [1] and vundle [2]. [1] https://github.com/tpope/vim-pathogen [2] https://github.com/gmarik/Vundle.vim

I might as well chime in too. I thought this was a fun way to get the motor-memory down for movement: http://vim-adventures.com/ And although I agree with the post you made, that everyone should know how the .vimrc file works, I use Vundle to help make my vim experience less painful: https://github.com/gmarik/Vundle.vim My biggest complaint about vim is probably a common one: the key commands don't seem to have much rhyme or reason. Perhaps in Bill Joy's mind they did but even now after years of use I find myself always having my vim cheat sheet nearby.

I think your experience hits on a problem with vim distributions - you're jumping into a solution to someone else's pain points. spf13, which has a lot of great plugins, probably started as someone's personal collection of plugins at some point. As such, the author had a lot of time to muse on what her/his current vim set up was missing. Sharing someone else's vim distribution, you miss out on the motivation behind including things (and also on the opportunity to pick alternatives more suited to your needs). I would start with stock vim and spend a few minutes outlining the features you need. I recommend, as a minimal set, a couple of plugins I think most people are happy about: Vundle [or Pathogen] (two managers for vim plugins hosted on GitHub) https://github.com/gmarik/Vundle.vim [https://github.com/tpope/vim-pathogen] Sensible