nott@unix.cis.pitt.edu (nancy nott) (01/20/90)
In the same vein as all of the posts about TECO, VAX, and PDP.... What does Emacs mean? just curious, nancy "I love you" is just another word for death.
mbrown@osf.org (Mark Brown) (01/20/90)
In article <21743@unix.cis.pitt.edu>, nott@unix.cis.pitt.edu (nancy nott) writes: > In the same vein as all of the posts about TECO, VAX, and PDP.... > What does Emacs mean? Emacs Makes A Computer Slow. Mark Brown IBM AWD / OSF | If a train station is where The Good mbrown@osf.org | a train stops, The Bad uunet!osf!mbrown| What happens at The Ugly (617) 621-8981 | a work station?
preston@titan.rice.edu (Preston Briggs) (01/20/90)
In article <2878@paperboy.OSF.ORG> mbrown@osf.org (Mark Brown) writes: >In article <21743@unix.cis.pitt.edu>, nott@unix.cis.pitt.edu (nancy >nott) writes: >> In the same vein as all of the posts about TECO, VAX, and PDP.... >> What does Emacs mean? > >Emacs >Makes >A >Computer >Slow. Well, that's harsh! More accurately, Extensible MACro. My favorites were on the LISP Machine: EINE and ZWEI Eine Is Not Emacs and Zwei Was Emacs (or Eine?) Initially Self-recursive acronyms, plus the series iterates, in German anyway.
cooleyra@clutx.clarkson.edu (Pixel,,,) (01/20/90)
From article <2878@paperboy.OSF.ORG>, by mbrown@osf.org (Mark Brown): > In article <21743@unix.cis.pitt.edu>, nott@unix.cis.pitt.edu (nancy > nott) writes: >> In the same vein as all of the posts about TECO, VAX, and PDP.... >> What does Emacs mean? > > Emacs > Makes > A > Computer > Slow. Ahhh...recursion. That explains it. > Mark Brown IBM AWD / OSF | If a train station is where > > The Good mbrown@osf.org | a train stops, > The Bad uunet!osf!mbrown| What happens at > The Ugly (617) 621-8981 | a work station? Pixel cooleyra@clutx. clarkson.edu | bitnet "Keep the wind in your solar sails..." --Glenn Clapp "here log (ln) changes to a different log (log)" (no reason given) --A.Fokas Disclaimer: opinions==mine; me<>cct
ncramer@bbn.com (Nichael Cramer) (01/20/90)
In article <4345@brazos.Rice.edu> preston@titan.rice.edu (Preston Briggs) writes: >My favorites were on the LISP Machine: EINE and ZWEI > Eine > Is > Not > Emacs >and > Zwei > Was > Emacs (or Eine?) > Initially >Self-recursive acronyms, plus the series iterates, in German anyway. For a Previous Employer, I had to write an easily-usable-by-VMS-and-other- business-weenies editor (that ran on the Lispm) which was named: DRIE DRIE Really Isn't EDT NICHAEL (...and, yes, I know it isn't spelled right.)
mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) (01/20/90)
In article <21743@unix.cis.pitt.edu> nott@unix.cis.pitt.edu (nancy nott) writes: >In the same vein as all of the posts about TECO, VAX, and PDP.... >What does Emacs mean? Editing MACroS. Work on EMACS started in the summer of 1976. The people who worked on it primarily at that time were Guy Steele, Richard Stallman, and Dave Moon. EMACS was written in TECO, but not the TECO that most people know. Most people know a very stripped-down and bastardized TECO which Bob Clements adapted for the DEC operating system for the PDP-6. The original TECO was written by Dan Murphy for the PDP-1, and later reimplemented on the PDP-6 (by, if I remember correctly, Richard Greenblatt, Jack Holloway, and Tom Knight in a single weekend!). The original TECO used a display scope to display the text being edited around the editing point. It remained a source of wonder and astonishment to the original authors of TECO that anyone ever used it without a display screen. This TECO ran on MIT's operating system for the PDP-6 and PDP-10, ITS (Incompatible TimeSharing). At Stanford, a different track of display editors had developed, again starting with the display scope on the PDP-1. The two surviving today are TVEDIT for Tenex/TOPS-20 and E for WAITS. Richard Stallman visited the Stanford AI Lab and was impressed by E's real-time editing facility. When he returned to MIT, he implemented so-called "^R mode" (a real time editing mode in TECO invoked by the CTRL/R command) in TECO. Although ^R mode made a whole new style of editing possible (unlike E and TVEDIT, the default action for newly typed in text was insert rather than replace), it was still rather primitive. The search was for a single character only, and you would still have to go back to TECO to do lots of things (such as read or write files!). Two major sets of TECO macro packages (a "macro" is a program, written in TECO, stored in a TECO register) developed; TECMAC and TMACS. TECMAC was a more real-time editor, while TMACS had a much richer set of functionality including named commands. Just about everybody had their own customizations on top of these packages. This was the situation when I worked at MIT in the summer of '76. I had brought with me my own favorite TECO-style editor, which, although it had only the functionality of primitive DEC TECO, had two interesting facilities: (1) it compiled all TECO programs (including commands) prior to execution, and (2) it had multi-character register names, which greatly increased the number of possible TECO registers to virtually infinite. Richard Stallman implemented the latter in TECO as part of the EMACS project, which was originally intended as a replacement for both TECMAC and TMACS. By New Years in 1977 EMACS had made significant inroads against TECMAC/TMACS; and in another year or so the older editors had both succumbed to software rot. Michael McMahon was irritated at the editor situation for Tenex and TOPS-20; the alternatives at that time ranged from TVEDIT to QED to TV (a DEC TOPS-20 TECO-like program with display terminal functionality much like that of the 1964 MIT TECO). He undertook the long and laborious task of porting MIT EMACS from ITS to Tenex and TOPS-20, and by 1978 EMACS was running on a small set of Tenex and TOPS-20 systems at MIT, Stanford, and SRI. Richard Stallman did heroic efforts to propagate the mass (and free) distribution to just about every TOPS-20 system in the work. This guaranteed EMACS a place in the sun. Without McMahon and Stallman's efforts we'd probably all be using vi or worse today. In the 1980's, TOPS-20 had reached its zenith. Because of horribly high maintenance costs (DEC was trying to shut down the product line in favor of VAX/VMS, and finally did in 1983), many sites were migrating from TOPS-20. Not trusting DEC, many sites picked UNIX as their migration path instead of VMS. There were a few critical TOPS-20 tools which "must" be ported before the migration; and one of those was EMACS. The rest is well-known... _____ ____ ---+--- /-\ Mark Crispin Atheist & Proud _|_|_ _|_ || ___|__ / / 6158 Lariat Loop NE R90/6 pilot |_|_|_| /|\-++- |=====| / / Bainbridge Island, WA "Gaijin! Gaijin!" --|-- | |||| |_____| / \ USA 98110-2098 "Gaijin ha doko ka?" /|\ | |/\| _______ / \ +1 (206) 842-2385 "Niichan ha gaijin." / | \ | |__| / \ / \ mrc@CAC.Washington.EDU "Chigau. Gaijin ja nai. kisha no kisha ga kisha de kisha-shita Omae ha gaijin darou." sumomo mo momo, momo mo momo, momo ni mo iroiro aru "Iie, boku ha nihonjin." uraniwa ni wa niwa, niwa ni wa niwa niwatori ga iru "Souka. Yappari gaijin!"
spl@mcnc.org (Steve Lamont) (01/20/90)
In article <21743@unix.cis.pitt.edu> nott@unix.cis.pitt.edu (nancy nott) writes: >In the same vein as all of the posts about TECO, VAX, and PDP.... >What does Emacs mean? It is one of those clever recursive acronyms: EMACS Makes All Computers Slow :-) spl (the p stands for press ctrl-meta-left-elbow to change all occurrences of foo to bar...) -- Steve Lamont, sciViGuy (919) 248-1120 EMail: spl@ncsc.org NCSC, Box 12732, Research Triangle Park, NC 27709 "That's People's Commissioner Tirebiter -- and NOBODY'S sweetheart!" - F. Scott Firesign
samlb@pioneer.arc.nasa.gov (Sam Bassett RCD) (01/20/90)
Then there was the CP/M word processing program (later mis-named "Perfect Writer") from Mark of the Unicorn: M I N C E I s o o m N t m a C p s E l e t e Sam'l Bassett, Sterling Software @ NASA Ames Research Center, Moffett Field CA 94035 Work: (415) 694-4792; Home: (415) 969-2644 samlb@well.sf.ca.us samlb@ames.arc.nasa.gov <Disclaimer> := 'Sterling doesn't _have_ opinions -- much less NASA!'
jet@flatline.UUCP (It's "Mr. Boyo" to you Dylan) (01/20/90)
In article <21743@unix.cis.pitt.edu> nott@unix.cis.pitt.edu (nancy nott) writes: >What does Emacs mean? "Emacs Makes A Computer Slow". It's recursive, too! Insert :-)'s where you feel they are needed. -- Skate UNIX J. Eric Townsend -- uunet!sugar!flatline!jet -- jet@flatline.lonestar.org EastEnders mailing list -- eastender@flatline.lonestar.org
jdarcy@pinocchio.encore.com (Jeff d'Arcy) (01/20/90)
nott@unix.cis.pitt.edu (nancy nott): > What does Emacs mean? jet@flatline.UUCP (It's "Mr. Boyo" to you Dylan): > "Emacs Makes A Computer Slow". It's recursive, too! In a similar vein, how about "Eats Memory And Compromises Security"? Jeff d'Arcy OS/Network Software Engineer jdarcy@encore.com Encore has provided the medium, but the message remains my own