One with Vim

#1

Post by fredoliveira » Thu, Jan 27, 2011, 5:56 PM UTC

One with Vim
invisibletheory.com

Re: One with Vim

#2

Post by pge » Thu, Jan 27, 2011, 6:48 PM UTC

"been around since 1991"?! while that's probably correct for vim proper, that ignores the much longer history of vi...

Re: One with Vim

#3

Post by fredoliveira » Thu, Jan 27, 2011, 6:53 PM UTC

pge wrote: post #2

"been around since 1991"?! while that's probably correct for vim proper, that ignores the much longer history of vi...

you are absolutely right - fixing this now. Vi has been around since the 70s, but I used the date for vim on the post - which was dumb of me.

Re: One with Vim

#4

Post by powdahound » Thu, Jan 27, 2011, 7:18 PM UTC

The Command-T plugin [1] was a big help in switching from TextMate to vim. I have no idea how anyone can be productive in vim without it (assuming you're working on a multi-file project).

1. https://wincent.com/products/command-t

Re: One with Vim

#5

Post by wccrawford » Thu, Jan 27, 2011, 7:20 PM UTC

powdahound wrote: post #4

The Command-T plugin [1] was a big help in switching from TextMate to vim. I have no idea how anyone can be productive in vim without it (assuming you're working on a multi-file project). 1. https://wincent.com/products/command-t

:e .

or

:NERDTree

Re: One with Vim

#6

Post by HerberthAmaral » Thu, Jan 27, 2011, 7:34 PM UTC

wccrawford wrote: post #5

powdahound wrote: post #4

The Command-T plugin [1] was a big help in switching from TextMate to vim. I have no idea how anyone can be productive in vim without it (assuming you're working on a multi-file project). 1. https://wincent.com/products/command-t

:e . or :NERDTree

Fuzzy Finder is also very useful http://www.vim.org/scripts/script.php?script_id=1984

Re: One with Vim

#7

Post by stevelosh » Thu, Jan 27, 2011, 7:39 PM UTC

wccrawford wrote: post #5

powdahound wrote: post #4

The Command-T plugin [1] was a big help in switching from TextMate to vim. I have no idea how anyone can be productive in vim without it (assuming you're working on a multi-file project). 1. https://wincent.com/products/command-t

:e . or :NERDTree

I use NERDTree and it's not even remotely close to Command-T (or PeepOpen, which is pretty much the same thing).

NERDTree is great for browsing your project and managing your files, but for opening files (when you know their names) you really can't beat the speed of Command-T/PeepOpen. They're in another league.

I don't know how people work without it.

Re: One with Vim

#8

Post by jmoiron » Thu, Jan 27, 2011, 7:44 PM UTC

powdahound wrote: post #4

The Command-T plugin [1] was a big help in switching from TextMate to vim. I have no idea how anyone can be productive in vim without it (assuming you're working on a multi-file project). 1. https://wincent.com/products/command-t

I've been using FuzzyFileFinderTextmate for a long time. I'm not sure it's still in active development, but it's worked just fine for me; is there a reason for me to switch to Command-T?

I also stick to buffers rather than tabs (for terminal/gui consistency) and use buftabs, which I quite like.

Re: One with Vim

#9

Post by swah » Thu, Jan 27, 2011, 7:47 PM UTC

Vim is easier on the hands, but Emacs (with ido-mode) still feels better for working with multiple files:

  (length (remove-if (lambda (b) (not (buffer-file-name b))) (buffer-list)))
  42

Re: One with Vim

#10

Post by gurraman » Thu, Jan 27, 2011, 7:51 PM UTC

swah wrote: post #9

Vim is easier on the hands, but Emacs (with ido-mode) still feels better for working with multiple files: (length (remove-if (lambda (b) (not (buffer-file-name b))) (buffer-list))) 42

There are multiple similar plugins for vim.