The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Donner <marc.donner@gmail.com>
To: Dan Cross <crossd@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Word erase?
Date: Mon, 8 Apr 2024 11:15:41 -0400	[thread overview]
Message-ID: <CALQ0xCBSMCpM7coBadhkkAtByk5TCt2h7W1JTicMjEKQoDL5BQ@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W5Jn7wPqjC-O3FFb7gZ=6ChXTJ_wY4MtCrKAJtRV+MkKQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]

In 1981 I was a grad student at CMU, which was running 4.1 or 4.2 at the
time.  I had spent the previous three years at IBM Research where someone
had built some editing stuff into the command line machinery for CMS.

I implemented some input line editing stuff both for the Perq and as a
module for the one of the UNIX shells and shared them with some of the
systems folks at CMU.  I do not know if they were adopted from my
implementations ... I am inclined to think not ... there was significant
skepticism of the value of command line editing among some of the systems
folks.

But the idea of retrieving previous command lines and editing the command
line was emerging as a thing in the early 1980s.
=====
nygeek.net
mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>


On Mon, Apr 8, 2024 at 11:03 AM Dan Cross <crossd@gmail.com> wrote:

> I wonder if anyone can shed any light on the timing and rationale for
> the introduction of “word erase” functionality to the kernel terminal
> driver. My surface skim earlier leads me to believe it came to Unix
> with 4BSD, but it was not reincorporated into 8th Edition or later,
> nor did it make it to Plan 9 (which did incorporate ^U for the "line
> kill" command).  TOPS-20 supports it via the familiar ^W, but I'm not
> sure about other PDP-10 OSes (Lars?).  Multics does not support it.
> VMS does not support it.
>
> What was the proximal inspiration?  The early terminal drivers seem to
> use the Multics command editing suite (`#` for erase/backspace, `@`
> for line kill), though at some point that changed, one presumes as
> TTYs fell out of favor and display terminals came to the fore.
>
>         - Dan C.
>

[-- Attachment #2: Type: text/html, Size: 2696 bytes --]

  reply	other threads:[~2024-04-08 15:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 15:02 [TUHS] " Dan Cross
2024-04-08 15:15 ` Marc Donner [this message]
2024-04-08 15:18 ` [TUHS] " arnold
2024-04-08 15:29   ` Warner Losh
2024-04-08 15:59     ` Lars Brinkhoff
2024-04-08 15:39   ` Larry McVoy
2024-04-08 16:06   ` Rich Salz
2024-04-09  1:51     ` Chris Torek
2024-04-12 15:58       ` Mary Ann Horton
2024-04-08 17:09   ` Steve Nickolas
2024-04-08 22:51   ` Mary Ann Horton
2024-04-12  1:29     ` Joseph Holsten
2024-04-08 16:14 ` Clem Cole

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=CALQ0xCBSMCpM7coBadhkkAtByk5TCt2h7W1JTicMjEKQoDL5BQ@mail.gmail.com \
    --to=marc.donner@gmail.com \
    --cc=crossd@gmail.com \
    --cc=tuhs@tuhs.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 NNTP newsgroup(s).