File1, 2, & 3 for tnguyen4:


INFO300

File1:

Editing with vi/vim is a fairly wide subject. This section contains
some interesting information for vi/vim users, as well as for those
learning to use vi/vim. It also contains vi/vim related stories,
such as how & why I began using vim (in 2005!).

Some of the articles were initially published as blog posts,
and the links below point to the original blog post. Apart from the actual
article content, you may find some comments there which are only relevant
to the moment they were written, I hope you will find the aeticles useful
nonetheless....

If you want to find more content related to other matters
such as developing a compiler and virtual machine,
extending Visual Studio, using the Cheetah template engine to
structure a web site, etc... visit the main NGEDIT articles section.


File2:

Yes, even if you can't believe it, there are a lot fans of the
30-years-old vi editor (or its more recent, just-15-years-old,
best clone & great improvement, vim).

No, they are not dinosaurs who don't want to catch up with the times
- the community of vi users just keeps growing: myself, I only got
started 2 years ago (after over 10 years of being a professional
programmer). Friends of mine are converting today. Heck, most vi
users were not even born when vi was written!

Yes, there are definite reasons why the vi/vim editing model is
just superior to any other out there. And you don't need to be a
Unix whiz to use it, either: vim is available for free for
almost any platform out there, and there are plug-ins to get
the functionality inside all major IDEs. Let's try to break a few
misconceptions, and see some real examples of why it's the killerest:

File3:

The first time you stumble into vi or vim, you are shocked and disgusted
that you have to use 'i' to start typing text. Can't remember which of
hjkl moves in which direction. And you need to press 'a' if you want to
insert after the last character of the line. Since you're already probably
used to other editors, and if the arrow keys work in insert mode (they do if
the system is configured properly, which is over 90% of the cases), you will
stay in insert mode and not go back to normal mode except if absolutely
necessary.
You'll probably spend 20 minutes with it, and never go back.
And also complaining: "How on earth am I going to remember whether I'm in
insert or normal mode?"

No lines are longer than 80 characters, TYVM. Other specified properties aren't being scored automatically at this time so this is not necessarily good news...