4 ms·
Why do you advocate using vim in a terminal? I prefer unite[1] to ctrl-p[2], it's much more flexible. 1: https://github.com/Shougo/unite.vim https://github.co
by shocks 12y ago
Why do you advocate using vim in a terminal?
I prefer unite[1] to ctrl-p[2], it's much more flexible.
1: https://github.com/Shougo/unite.vim https://github.com/Shougo/unite.vim
2: https://github.com/kien/ctrlp.vim https://github.com/kien/ctrlp.vim
- wahnfrieden 12y agoI wanted to like unite, but couldn't get it to behave as I expected: when opening a file via unite, it doesn't respect the active window, it ignores the splits I have. IIRC it always opened the file in the top left window.
- shocks 12y agoThat's weird. Unite doesn't exhibit this behaviour for me. My config is here: https://github.com/wridgers/vimto/blob/master/rc/25-unite.vim https://github.com/wridgers/vimto/blob/master/rc/25-unite.vi...
- wahnfrieden 12y agoThanks, will give it another shot with your config.
- swartkrans 12y agoI also prefer cntrlp, it's much more performant in my experience.
- sooheon 12y agoThis is true (something like junegunn's fzf is even faster than either), but I think the tradeoff is between performance and consistency of interface. Unite can provide the same interactions for recent files, buffers, file navigation, grep results, etc.
- tomjakubowski 12y agoYou can do this with ctrlp too. The standard sources are files, buffer, and MRU files, but it comes with extensions for things like the quickfix list (grep results), tags, and scripts in the runtime path. You can also write your own: https://github.com/kien/ctrlp.vim/tree/extensions https://github.com/kien/ctrlp.vim/tree/extensions
- shocks 12y agoReally? With unite you can use vimproc to fork out the searching process. Much quicker. Using unite and ctrlp with a 30k file source base, ctrlp was far to slow for me.