News for hackers. Stuff that matters.
Re:Sublime Text 2.0 Released by geoffw8 on Tuesday June 26, 2012 @10:45AM (#4162081)
I started writing the same thing, and thought I'd just add onto this instead. Tried using Vim because I like the look of how flexible it is to tile windows, but I just cannot move away from Sublime's file search.

I don't even click tabs that I have open any more, I just hit Apple + p and start typing say g-l-o for global.css and I know its there, hit enter and voila.

Like you say, multi-platform too, so I get to use it on my little Ubuntu netbook and on my iMac. Love it. Really should buy a licence.

Re:Sublime Text 2.0 Released by vaneck on Tuesday June 26, 2012 @11:01AM (#4162209)
Command-T gives you similar functionality in Vim. It's great.

https://github.com/wincent/Command-T

Re:Sublime Text 2.0 Released by agscala on Tuesday June 26, 2012 @11:07AM (#4162248)
CtrlP is newer and is arguably much better than Command-T

https://github.com/kien/ctrlp.vim

Re:Sublime Text 2.0 Released by xyzzyb on Tuesday June 26, 2012 @11:28AM (#4162393)
Yes, CtrlP is faster and easier to install because it's just a vimscript. It also supports all of Command-T's functionality, so it's pretty much just great.
Re:Sublime Text 2.0 Released by geoffw8 on Tuesday June 26, 2012 @12:26PM (#4162729)
Hey, what agscala says below is absolutely right. I tried it, but honestly, Sublime Text 2 is far superior. Even my Vim-core colleague to my right agrees. And thats saying something!

Edit: Scrap that, rush-read - CntrlP doesn't beat Sublime's Apple+P. Honestly, try it and you'll see what I mean.

Re:Sublime Text 2.0 Released by UrLicht on Tuesday June 26, 2012 @11:31AM (#4162415)
I've found Command-T slows way down on large trees, causing a very noticeable interruption in my "flow" when I use it. Also, it's written in ruby which can be a bit more painful to get started with if your distro doesn't compile ruby support into vim by default.
Re:Sublime Text 2.0 Released by notJim on Tuesday June 26, 2012 @12:52PM (#4162875)
Do you find that it slows down only the first time you use it within an editing session, or everytime you use it? If only the first time, I've got a fork which caches the files to disk, so that you don't hit that slowdown very often. The downside is that when you add new files, you have to bust that cache.