Linked by Tony Steidler-Dennison on Tue 8th Jul 2008 15:19 UTC
Linux I find a large number of people around me who have used vim a few times while writing programs. Very few of them have grown into becoming effective vim users. The majority drop out because of its initially daunting interface. A good number of the interested users switch to emacs, because they think the 'power' just isn't there with vim. I am not saying emacs is bad, but I just cannot stand decisions made on lack of information.
Order by: Score:
libray
Member since:
2005-08-27

I found the following helpful for cases where you are on a system and want to turn off some very annoying vim settings.

http://www.vim.org/tips/tip.php?tip_id=330

Add to personal .vimrc:
set nocindent
set nosmartindent
set noautoindent
filetype indent off

I use this in case a GNU system already has vim that I didn't remove and already replace with nvi.

Comment by moleskine
by moleskine on Tue 8th Jul 2008 15:56 UTC
moleskine
Member since:
2005-11-05

Debian have a reference card for the main commands in vim. I think it comes as a pdf. It fits exactly on two sheets of A4, so you can double-side it, laminate it and keep it around - very handy. I'm sure the card doesn't cover nearly enough ground for the serious user or programmer, but it's really helpful for lighter stuff: editing config files or dealing with no-X things, like editing a file on another machine over ssh. For quick and simple things, I reckon joe has a lot going for it even though it's not nearly as powerful. But I find joe's commands easier to remember for some reason.

vim cheat compound
by lavish on Tue 8th Jul 2008 16:35 UTC
lavish
Member since:
2006-12-30
RE: vim cheat compound
by Glynser on Fri 11th Jul 2008 10:52 UTC in reply to "vim cheat compound"
Glynser Member since:
2007-11-29
Quoting
by averycfay on Tue 8th Jul 2008 16:50 UTC
averycfay
Member since:
2005-08-29

If your summary is just a quote from the story, can you put quotes around it and possibly also put it in italics? For example, see most of Thom's news postings.

Nice Intro/Tutorial
by DoctorPepper on Tue 8th Jul 2008 17:32 UTC
DoctorPepper
Member since:
2005-07-12

I've been a Vim user for many years now, but since we just got Vim installed on our development server, I shared this intro/tutorial with the rest of my team.

Good article but....
by pstreck on Tue 8th Jul 2008 20:32 UTC
pstreck
Member since:
2005-07-17

I thought this article was filled with a lot of good tidbits, however one comment was made that made me cringe!

I assume you know how to split windows, and all that jazzy stuff.

This is the one feature that totally expected to be covered. Every time I use vim and the split window feature with someone next to me they are instantly like "WOW! How do you do that?" I think this is one of vims most flexible and underused features that should have been granted space in this article. Especially when insertion and copy/paste functions are covered. I give this article a B+ overall, but come on guy! Cover the split windows.

RE: Good article but....
by DoctorPepper on Tue 8th Jul 2008 22:42 UTC in reply to "Good article but...."
DoctorPepper Member since:
2005-07-12

I agree totally. Splitting windows is one of my "neat" selling points for Vim, to my hard-core vi-user friends. Once they see me split a window horizontally, then resize them, and split the top window vertically, they become totally impressed.

Actually, my best selling point is when I edit multiple files, and show how to move between them, then copy and paste between buffers.

Oh, and we won't even talk about the syntax highlighting. That's always good for a few "oooh"'s and "ah"s. :-)

screen + mc + vim
by acobar on Tue 8th Jul 2008 23:26 UTC
acobar
Member since:
2005-11-15

These are my killing CLI all time favorites.

RE: screen + mc + vim
by Doc Pain on Wed 9th Jul 2008 01:07 UTC in reply to "screen + mc + vim"
Doc Pain Member since:
2006-10-08

[screen + mc + vim] are my killing CLI all time favorites.


Wow, so I'm not the only one out there! :-) Personally, I like the mcedit, too, but it's not as handy when terminal emulation is not very good.

Really useful
by PlatformAgnostic on Wed 9th Jul 2008 07:05 UTC
PlatformAgnostic
Member since:
2006-01-02

I do most of my editing in VIM, but it looks like I've been only scratching the surface here. Thanks for the good article.

Comment by Bending Unit
by Bending Unit on Wed 9th Jul 2008 07:48 UTC
Bending Unit
Member since:
2005-07-06

I once made an effort to learn vim and emacs because if they are so hard to use, they must be superior right?

But now I only use the basics in vim when I have to and avoid emacs. Coding is done in a real IDE and for other tasks I use editors that are both powerful and usable without reading books and tutorials.

Life is too short for vim.

RE: Comment by Bending Unit
by Johann Chua on Wed 9th Jul 2008 10:52 UTC in reply to "Comment by Bending Unit"
Johann Chua Member since:
2005-07-22

Learning vi or vim seems to be most useful if you're on a *nix terminal, since the server is bound to at least have vi (emacs is more resource-heavy). I actually have a used copy of the O'Reilly vi book, but I don't use or admin headless servers, so I just use GUI text editors.

Vim : my main editor
by ArcadeFX on Wed 9th Jul 2008 11:20 UTC
ArcadeFX
Member since:
2005-07-06

I really like Vim and used it on small to large scale projects. It has helped me create a video game (in C for Linux PDA), cms system (content mgt in PHP5) and a bunch of other projects.

I also now use Komodo Edit (free ed.) and it's nice as well. Sometimes a full GUI is nice.

Of course having a background as a Linux/Unix admin. Vi/Vim has served me well (Perl, Shell, Python scripting).

Go Vim!