Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cs.utexas.edu!sm.unisys.com!csun!polyslo!dorourke
From: dorourke@polyslo.CalPoly.EDU (David M. O'Rourke)
Newsgroups: comp.sys.mac
Subject: Re: Aztec C/Shell DOES HAVE a 'vi' editor
Message-ID: <4616@polyslo.CalPoly.EDU>
Date: 14 Oct 88 16:43:40 GMT
References: <1988Oct10.145745.2790@mntgfx.mentor.com> <967@oswego.Oswego.EDU> <5606@hoptoad.uucp> <10402@dartvax.Dartmouth.EDU>
Reply-To: dorourke@polyslo.UUCP (David M. O'Rourke)
Organization: Cal Poly State University -- San Luis Obispo
Lines: 22

In article <10402@dartvax.Dartmouth.EDU> earleh@eleazar.dartmouth.edu (Earle R. Horton) writes:
>In article <5606@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>>What on Earth does vi give you that a good Mac editor doesn't?  
>
>Tags, automatic backup files.

  There are a couple of Mac editor's that offer this capability.

  Both MPW & Qued/M+ offer tags or markers for the text.  In addition Qued/M+
offers backup files, autosaving, and collapsalbe {sp?} lines so that you
can "hide" lines of code under their procedure headers so you don't have
to look at them every time you run through a listing.  Also both Qued/M+ &
MPW offer macros for repetitive processes.  MPW has a scripting language that
can do this, and Qued/M offers a Macros Language of it's own.
  For features I still haven't seen one feature of 'vi' that can't be found
in good Macintosh editor's.  The only "feature" of vi is that it's a pain to
use and/or figure out.  And Mac editors tend to be straght forward.
-- 
David M. O'Rourke                                  dorourke@polyslo.calpoly.edu

"If it doesn't do Windows, then it's not a computer!!!"
Disclaimer: I don't represent the school.  All opinions are mine!