Live data from Hacker News

Why I use vim

michaeltrier.com

1–10 of 56 posts

Re: Why I use vim

#2
The speed increase on paragraph editing capabilities is really attracting versus pointing your mouse to do everything. I'm gonna give it a shot, thanks.

Re: Why I use vim

#3
post #2

The speed increase on paragraph editing capabilities is really attracting versus pointing your mouse to do everything. I'm gonna give it a shot, thanks.

If you're just starting, I strongly recommend you go through vimtutor. After installing vim, just type "vimtutor" in your shell.

Then, head over to #vim on freenode.net with any questions. Even simply lurking in that channel is a great education.

Re: Why I use vim

#4
This is helpful, particularly the resources listed, but I would advise against using someone else's config starting out. Continually editing my own .vimrc for the first few months was a big part of learning. If you use someone else's dotfiles right from the start, there's a good chance you'll end up believing some behaviour is default when it really isn't, and that's going to mess you up.

Re: Why I use vim

#5
post #2

The speed increase on paragraph editing capabilities is really attracting versus pointing your mouse to do everything. I'm gonna give it a shot, thanks.

It took me two weeks before I finally grew comfortable with vim, so don't get discouraged. Start off by treating it as a regular text editor. Use the arrow keys to move around, use control (windows) or option (mac) + arrow keys to quickly move between words, etc. Slowly introduce a few vim shortcuts at a time. It was also helpful for me to write the commands on a whiteboard or a post it and have it on my monitor as reference.

Re: Why I use vim

#6
post #4

This is helpful, particularly the resources listed, but I would advise against using someone else's config starting out. Continually editing my own .vimrc for the first few months was a big part of learning. If you use someone else's dotfiles right from the start, there's a good chance you'll end up believing some behaviour is default when it really isn't, and that's going to mess you up.

That was a huge mistake for me when first learning vim. If you start with someone else's .vimrc, you will run into a lot more "FML, what is going on" experiences that you should.

Re: Why I use vim

#8
Every week there's some post like this, or "why I switched back and forth between Vim and Textmate 17 times", and, frankly, I just don't see the merit in it. Are you trying to get other people to use the editor you like?

Re: Why I use vim

#9
post #8

Every week there's some post like this, or "why I switched back and forth between Vim and Textmate 17 times", and, frankly, I just don't see the merit in it. Are you trying to get other people to use the editor you like?

From the HN Guidelines:

"Please don't submit comments complaining that a submission is inappropriate for the site. If you think something is spam or offtopic, flag it by going to its page and clicking on the "flag" link. (Not all users will see this; there is a karma threshold.) If you flag something, please don't also comment that you did."

http://ycombinator.com/newsguidelines.html

Re: Why I use vim

#10
post #4

This is helpful, particularly the resources listed, but I would advise against using someone else's config starting out. Continually editing my own .vimrc for the first few months was a big part of learning. If you use someone else's dotfiles right from the start, there's a good chance you'll end up believing some behaviour is default when it really isn't, and that's going to mess you up.

Agreed. There's a great post Vim: revisited with a minimal .vimrc file that I used after having to start over learning Vim because of using someone else's .vimrc I didn't need or fully understand: http://mislav.uniqpath.com/2011/12/vim-revisited/
Post reply on HN