Xref: utzoo comp.editors:1312 comp.sys.dec:2636
Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!jarthur!polyslo!jdudeck
From: jdudeck@polyslo.CalPoly.EDU (John R. Dudeck)
Newsgroups: comp.editors,comp.sys.dec
Subject: Re: DEC EDT-like editor
Message-ID: <25d3123c.19aa@polyslo.CalPoly.EDU>
Date: 9 Feb 90 18:55:56 GMT
References: <825@larry.sal.wisc.edu> <20570@watdragon.waterloo.edu> <26650@cup.portal.com> <9708@ttidca.TTI.COM>
Reply-To: jdudeck@polyslo.CalPoly.EDU (John R. Dudeck)
Distribution: na
Organization: Cal Poly State University -- San Luis Obispo
Lines: 20


In article <9708@ttidca.TTI.COM> kevin@ttidcb.tti.com (Kevin Carothers) writes:
>In article <26650@cup.portal.com> Zaft@cup.portal.com (Gordon Christopher Zaft) writes:
>>GNU Emacs has both an EDT emulation mode and a vi emulation mode.
>>
>
> I just have to ask.       Why not just use "vi"?

In Feb 1987 Dr. Dobb's Journal had an issue with a cover article entitled
Text Editors: The Baby Duck Syndrome.  The article wasn't especially
enlightening, but one sentence summarized it all:

  "Like ducklings that adopt the first moving object they see as a mother,
  programmers often adopt the first editor they learn as the model of
  what an editor is and should be."

Personally I still prefer EDT as an editor, although I do almost all my
editing on a pc now, using Logitech Point, which beats EDT for my needs.
The only way I survive trying to use vi is to hang a cheat sheet in my
Curtis Clip copyholder on the side of my screen...

-- 
John Dudeck                           "You want to read the code closely..." 
jdudeck@Polyslo.CalPoly.Edu             -- C. Staley, in OS course, teaching 
ESL: 62013975 Tel: 805-545-9549          Tanenbaum's MINIX operating system.