[taf2]

cmd+t lookup is not a good vim thing... it's slow requires me to move my hand to the right to navigate using arrow keys... also it's slow. changing files takes significantly longer... it's bad enough how slow the iterm.app is on osx and don't even get me started on the slowness of the terminal.app -- picky vim user

update: i like the empty line space indicators little boxes look cool

[pfranz]

You can hold down CTRL and use j/k to move up/down (so you don't have to use the arrow keys). It can be slow on very large directories.

I switched to CtrlP last week because I switched OSes at work and didn't want to recompile vim and Cmd+t. In the past CtrlP was significantly slower, but I found a few new features that actually makes it faster than Cmd+t for me; it automatically navigates up looking for a .git or .svn to search from instead of cwd, and you can set up caching (persistent between sessions) and max num of files to scan--I believe you can set a timeout, too. I also setup a filter so my build folder and docs won't show up.

Since finding Cmd+t, it's been the fastest way to navigate to files in a project (especially when they're not in the same directory).

[johncoltrane]

The whole point of Command-T, FuzzyFinder, CtrlP and friends is to provide "fuzzy" completion. They don't display a list of files for you to navigate with the arrows they display a list of candidates that you refine by typing more characters.