Nuxified GNU/Linux Help Forums - vi survival guide - Comments

Looks like you're posting

libervisco — Fri, 06 Apr 2007 03:24:43 +0200

Looks like you're posting replies around this site that are barely related to the subject matter just to promote your web site. However this is no way to promote your web site nor a way to participate on any site, because it is obviously non-genuine.

If I would let everyone do that we'd have quite a mess here, which is why I deleted your other comments and are replying to this one here.

Your site *may* be about charity, but that doesn't change the rules. There are better ways to promote it than spamming (which this pretty much is).

Thank you

reply

donate car — Fri, 06 Apr 2007 02:47:41 +0200

yes it covers all you need to get started.

When I first started this

neocontrol — Fri, 14 Jul 2006 17:31:42 +0200

When I first started this job (Linux Sys admin), I had minimal linux experience. Pretty much just a home network that I toyed around with. I never liked vi cause I didn't like moving around without the arrow keys. So I always used JOE. When I got here, I found out that I didn't have joe here. Forced to learn vi. After the short learning curve, about 2 weeks, I can't go back to anything else. To powerful and useful. And now I can see why things are arranged such as they are. It's great.

Nice guide

dylunio — Sat, 08 Jul 2006 17:25:15 +0200

I've finnally got around to reading this - I must say it's very good and shall be using it for any progrmming projects I have.

Grand work

I always thought the only

tbuitenh — Wed, 24 May 2006 20:53:41 +0200

I always thought the only way to survive emacs was to stay away from it...?

Just kidding. To each his own editor.

Nice article

mbishop — Wed, 24 May 2006 20:13:59 +0200

You're gonna make me want to write an "Emacs survival guide" though

REPLACE mode

tbuitenh — Tue, 23 May 2006 15:43:47 +0200

If you need to replace more than one character, try REPLACE mode. I don't think plain old vi has it, but in vim you can enter it with (shift+)R . (lowercase r replaces a single character).

Well done free-zombie. This

AndrewB — Tue, 23 May 2006 10:59:29 +0200

Well done free-zombie. This guide rocks!

Good One

Anonymous — Mon, 22 May 2006 14:11:57 +0200

Indeed vim is one of the best editors one cld opt for
ESC ZZ

the most important

Anonymous — Mon, 22 May 2006 11:32:52 +0200

you only need to know :wq!

Somehow that doesn't

tbuitenh — Sun, 21 May 2006 14:54:09 +0200

Somehow that doesn't surprise me. Eclipse thinks it's an operating system not an editor, so vi should be ported to it

except those that buy the

free-zombie — Sun, 21 May 2006 13:42:49 +0200

except those that buy the eclipse vi plugin
yep, there is one. Proprietary and commercial. Based of two pieces of free software: vi and eclipse.

vi saves the day

tbuitenh — Sun, 21 May 2006 12:33:07 +0200

I have to use eclipse for a university project, since I need specific software that has been implemented as an eclipse plugin. Of course this plugin depends on other plugins, which makes a nice dependency hell. To make things worse, the person who developed that plugin uses windows, and I use linux, so I can't just copy his eclipse installation. To figure out which plugins are still missing I asked him for the output of DIR in his plugins directory. A few dd's and a [control-v][select]d in vi, a sort and then a diff with the output of ls in my own plugins directory, and it becomes clear which plugins I need. I'd like to see anyone do that on windows+eclipse

Nice article

Anonymous — Sat, 20 May 2006 18:19:33 +0200

Seriously, i've never seen such a good and condenced article about vi.

I wonder what a day without vim would be for me ...

mouse

Anonymous — Sat, 20 May 2006 11:23:48 +0200

the mouse was invented in the garden if eden 6,000 years ago.

vi survival guide

free-zombie — Thu, 18 May 2006 23:17:50 +0200

If you are trying to work at a command line in pretty much any Operating System, no matter if it is a GNU/Linux brand such as Ubuntu or Fedora Core, another UNIX-like system like Mac OS X or FreeBSD or even Microsoft Windows, you will most definately need a text editor sooner or later. If you are using a UNIX-like system, like GNU/Linux variants, there are many text editors that may or may not be installed. Luckily there is one de-facto standard:
vi is included in almost every GNU/Linux or UNIX distribution. "vi" is a truncation of the word "visual" and has, contrary to popular belief, nothing to do with the Roman number 6. Many people are not too fond of vi, but are, alas, often forced into using it when it is the only known option. You may prefer easier editors like gedit (Gnome), kate (KDE), emacs or ne (command line), but these may not be present when working at the command line.
Therefore, it is best to know at least the basics of vi and to understand it a little better; the basics of survival in vi, which you will learn in this guide. Unlike what you may have heard about the invention of the language C, the vi editor was not the idea of some kind of sick joke. It was for real and it served a real purpose. I am writing this in vi.