From: Richard Stallman <rms@gnu.org>
To: John Yates <john@yates-sheets.org>
Cc: brandelune@gmail.com, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: "Point" vs. "cursor" in documentation
Date: Wed, 04 Jul 2018 18:32:58 -0400 [thread overview]
Message-ID: <E1faqKY-0004DT-P3@fencepost.gnu.org> (raw)
In-Reply-To: <CAJnXXoj=i4W1=QvT7uWVzy9=DbmazO8raeE9e+k5OtuKyOy36w@mail.gmail.com> (message from John Yates on Wed, 4 Jul 2018 08:13:22 -0400)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I had no exposure to ITS and so have no knowledge of its history
> or the tools that it offered. Was TECO truly its first editor?
Yes. PDP-10 TECO came before ITS.
The PDP-10 was an upward-compatible improvement of the PDP-6.
The AI lab first got a PDP-6 and wrote a TECO for it.
The PDP-6 was not suitable for timesharing. So when it got the
PDP-10, people immediately used TECO on that too, but they also wrote
ITS.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2018-07-04 22:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 13:25 "Point" vs. "cursor" in documentation Siraphob (Ben) Phipathananunth
2018-07-03 14:27 ` Drew Adams
2018-07-03 14:37 ` Jean-Christophe Helary
2018-07-03 20:16 ` John Yates
2018-07-03 23:04 ` Richard Stallman
2018-07-04 12:13 ` John Yates
2018-07-04 15:15 ` Eli Zaretskii
2018-07-04 17:20 ` Drew Adams
2018-07-04 22:32 ` Richard Stallman [this message]
2018-07-04 23:03 ` John ff
2018-07-04 2:27 ` Siraphob (Ben) Phipathananunth
2018-07-04 2:39 ` Stefan Monnier
2018-07-04 6:21 ` Jean-Christophe Helary
2018-07-04 14:52 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1faqKY-0004DT-P3@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=brandelune@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.