Path: utzoo!attcan!uunet!cs.utexas.edu!usc!srhqla!quad1!ttidca!kevin From: kevin@ttidca.TTI.COM (Kevin Carothers) Newsgroups: comp.editors Subject: Re: vi (vs VMS/EDT) Keywords: DEC bashing Message-ID: <7865@ttidca.TTI.COM> Date: 20 Nov 89 20:34:57 GMT References: <1989Nov14.223604.17418@cs.eur.nl> <1989Nov15.202718.12762@ux1.cso.uiuc.edu> <6995@ficc.uu.net> <3328@jhunix.HCF.JHU.EDU> Reply-To: kevin@ttidcb.tti.com (Kevin Carothers) Organization: Citicorp/TTI, Santa Monica Lines: 36 In article <3328@jhunix.HCF.JHU.EDU> jeburke@jhunix.UUCP (John Burke) writes: >In article <6995@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes: >> >>You can't edit another file without quitting the file you're working on and >>going back to DCL or MCR. Discovering this was one of those "you've GOT to >>be kidding" experiences. You know, like the first time you found out about >>segments on the 8086. >> >>`-_-' Peter da Silva . > >(As my English teacher in high school taught me to say...) This turns >out not to be the case. In fact, it is trivial to edit using multiple >buffers in EDT. If you have a manual set available, try looking up >multiple-buffer operations. Specifically, look up "=name" and "find >=name". It's actually not much clunkier than EMACS for movement >between buffers, and it certainly beats the hell out of vi with >respect to _any_ operation utilizing multiple buffers. > J. Burke is indeed correct. Funny. It seems like whenever someone posts that an editor can't do something, someone comes around a day later and completely disproves the statement :) EDT was fantastic with cut-paste, and multiple-buffer features. I too used to use and love EDT. Often, I wonder if there is a PD UNIX compatible version which can run on window environs. One thing I believed EDT was poor on was macro definition [Although someone out there probably has an easy way to do it :)]. I DO remember the RSX-11M manuals to be pretty lousy on the usage of EDT, though. Does anyone remember the name of the DEC editor that had that spiffy "learn" mode? It seems that would be easy as stink to add to Vi and would make vi the "ultimate" macro-easy editor. -- Kevin Carothers {philabs,csun,psivax}!ttidca!kevin