Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac
Subject: Re: Aztec C/Shell DOES HAVE a 'vi' editor
Message-ID: <5606@hoptoad.uucp>
Date: 12 Oct 88 15:57:17 GMT
References: <1988Oct10.145745.2790@mntgfx.mentor.com> <967@oswego.Oswego.EDU>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 24

I may be opening up a rather large can of worms here; but why, why, why
would anyone want to use a single-window editor on a windowing OS?  Sure,
you get regular expression search (just like MPW Shell and QUED and the
Lightspeed C editor).  Sure, you get a command set you have to memorize,
and modal behavior, if that's the kind of kinky computing you're into.
But how can you do good programming without the ability to open your
include files and tile them with your source files?  How can you do good
BBSing without the ability to open your log files and look in them?
What on Earth does vi give you that a good Mac editor doesn't?  Aren't
multiple windows a rather large advantage?

By the way, I've used vi for about six years.  I'm using it now, because
I don't feel like learning a new flavor of Emacs.  I'm doing it using my
terminal emulator (TOPS Terminal) so I can open up any local file in
the built-in editor if I want.  I know vi, and I know the Mac, and the Mac
is better.

Now, a Mac Emacs is a different story....
-- 
Tim Maroney, Consultant, Eclectic Software, sun!hoptoad!tim
"What's bad? What's the use of turning?
 In Hell I'll be there a-burning!
 Meanwhile, think of what I'm earning!
 All on account of my name." - Bill Sykes, "Oliver"