91–99 of 99 posts
I prefer CtrlP to CommandT, since it does not requires external programs. https://github.com/kien/ctrlp.vim
I have strange issues with CtrlP, especially files not being found although they would be a clear match.
Earlier quoted context omitted.
As others have said CtrlP is slower; but not having the Ruby dependency makes it _far_ less of a headache to install on Windows, should you ever find yourself on such a machine.
Installing command-t is fairly easy on windows. Just compile as instructed with latest ruby 1.9 + devkit and replace gvim.exe with the one specified in this page https://wincent.com/comments/6544 .
Earlier quoted context omitted.
pathogen requires you to roll your own submodule thingy. This is certainly feasible if you know git well, but vundle is still easier
Not sure where you got that idea: I use pathogen without involving Git at all.
Earlier quoted context omitted.
In my experience, it's better to spend a long time playing with Vim, and then look at plugins. There's a lot that Vim does out of the box without any additional tools, and spending time learning to use (some) of it without trying to make it more like another editor is the only way you're going to get better at it. Learn about buffers and how to manage them before using BufExplorer. Learn the (many) movement keys, and…
I disagree. As someone who started using Vim recently, the issue wasn't learning modes/key sequences as it was just reaching feature parity with my previous editor (note that doesn't mean "acts like my previous editor", just "is at least as capable as my previous editor"). If I can't open files really quickly, I feel lost and upset, so I took care of that very early in the learning process by setting up CtrlP. Same w…
My favorites: * pathogen [1] * PreciseJump [2] * MRU [3] * scratch [4] * xptemplate [5] * renumber [6] [1] - http://www.vim.org/scripts/script.php?script_id=2332 [2] - http://www.vim.org/scripts/script.php?script_id=3437 [3] - http://www.vim.org/scripts/script.php?script_id=521 [4] - http://www.vim.org/script.php?script_id=389 [5] - http://www.vim.org/scripts/script.php?script_id=2611 [6] - http://www.vim.org/scripts…
Use vundle instead of pathogen - it installs the plugins for you, so managing them in source control is much easier. Lines in a vimrc are much less of a headache than git submodules etc.
I disagree. This may be true if you don't understand git submodules, but git submodules are not hard to understand with just a little effort. Once understood, git submodules are very easy to work with.
Also, this may be just a personal quirk, but I'm not very fond of managing vim from within vim. It would bug the living daylights out of me to load vim just to update my plugins. I'm probably the only one who feels that way, though.
Earlier quoted context omitted.
pathogen requires you to roll your own submodule thingy. This is certainly feasible if you know git well, but vundle is still easier
Not sure where you got that idea: I use pathogen without involving Git at all.
Earlier quoted context omitted.
Or OSX where I can never seem to get vim to build from source (which is the only option for Ruby or even Python integration). I know I've done it in the past but every time I need to I forget the magic I need to do.
Just use MacVim and the bundled mvim. Open file in MacVim: $ mivm file Open file in Vim: $ mvim -v file
Earlier quoted context omitted.
Not sure where you got that idea: I use pathogen without involving Git at all.
OK, then you have some kind of shell script to do the downloads, or you do them all manually each time. These are not better alternatives