From: "Ludwig, Mark" <ludwig.mark@siemens.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: EMACS, 1976
Date: Wed, 25 Jul 2012 16:53:34 +0000 [thread overview]
Message-ID: <BC5672F8AD4C054BAF167C9801500D1A9B9A8374@USCIMMBX003.net.plm.eds.com> (raw)
In-Reply-To: <juos8p$mab$1@newscl01ah.mathworks.com>
> From: Peter Davis
> Sent: Wednesday, July 25, 2012 8:28 AM
> To: help-gnu-emacs@gnu.org
> Subject: Re: EMACS, 1976
>
> On 7/25/2012 6:36 AM, Barry Margolin wrote:
> > In article <mailman.5547.1343209085.855.help-gnu-emacs@gnu.org>,
> > Mark Skilbeck <m@iammark.us> wrote:
> >
> >> Hello, fellow Emacsen (Emacsians?).
> >>
> >> I've been reading RMS's essay, EMACS: The Extensible, Customizable
> >> Display Editor[0], and it's piqued an interest in me; I would like to
> >> view the code that made up the first EMACS release in 1976. Have it
> >> any of you lads and lasses, or know where it I may find?
> >
> > I googled for "teco emacs" and found this:
> >
> > http://pdp-10.trailing-edge.com/mit_emacs_170_teco_1220/index.html
> >
> > Good luck understanding TECO.
> >
>
> I must still have some TECO reference cards around somewhere. I remember
> writing whole applications as TECO macros. Fun.
Yeah, I started hacking EMACS on a DECsystem-2060 (a.k.a. "Twenex") circa 1980. I did all my EMACS customization work in Lisp, in the equivalent of would now be a .el file, and byte-compiled it to a library file that I subsequently loaded -- just like what we do today.
What I remember having to learn were the TECO display codes. For example, if I recall correctly (ahem, yes, it really was >30 years ago!), Control-P was the character to "home up" in the minibuffer (which was three lines tall back then), meaning move the cursor to the upper-left-most character position. Then there was another character to delete the remainder of the space which I don't remember; those two characters appeared frequently in the out-of-the-box EMACS code, because any prompting function had to do that in order for its prompt to appear cleanly and consistently.
Oh, and at the time, I liked to "sign" my e-mail messages with "$$" at the end. What will not be clear by just looking at a printed representation of TECO is that the dollar sign ("$") is how an ESCape character appears; ESCape-ESCape was the statement terminator, and interactively meant "execute the preceding code."$$
next prev parent reply other threads:[~2012-07-25 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5547.1343209085.855.help-gnu-emacs@gnu.org>
2012-07-25 10:36 ` EMACS, 1976 Barry Margolin
2012-07-25 11:44 ` Mark Skilbeck
2012-07-25 13:14 ` Doug Lewan
2012-07-25 13:27 ` Peter Davis
2012-07-25 16:53 ` Ludwig, Mark [this message]
2012-07-25 9:37 Mark Skilbeck
2012-07-25 9:43 ` Peter Dyballa
2012-07-25 9:52 ` Mark Skilbeck
2012-07-25 9:44 ` Mark Skilbeck
2012-07-26 14:57 ` François Allisson
2012-07-26 15:13 ` Mark Skilbeck
2012-07-26 20:26 ` Christophe Poncy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BC5672F8AD4C054BAF167C9801500D1A9B9A8374@USCIMMBX003.net.plm.eds.com \
--to=ludwig.mark@siemens.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).