From: Larry McVoy <lm@mcvoy.com>
To: arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Word erase?
Date: Mon, 8 Apr 2024 08:39:58 -0700 [thread overview]
Message-ID: <20240408153958.GL16155@mcvoy.com> (raw)
In-Reply-To: <202404081518.438FIflK003772@freefriends.org>
On Mon, Apr 08, 2024 at 09:18:41AM -0600, arnold@skeeve.com wrote:
> 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.
>
> My memory jibes with this -- through V7 defaults were # and @, and BSD
> changed to ^H / DEL and ^U. ^W was a BSD thing, probably inspired by
> TOPS-10.
>
> There was a patch on USENET that added ^T to print the load average that
> we put into the vax at Georgia Tech. A professor who'd come to us from MIT
> saw it and was surprised tht we could do it on Unix. :-)
I loved and hated ^T. Logged into a 4MB Vax 780 running 4.x BSD
with 40-50 other students, the only thing that was responsive was ^T.
I really wonder how much slower that Vax was because we were all hitting
^T wondering when our compile would be done.
It was around then that I bought a 128K floppy only CP/M machine.
Slower than the Vax but it was all mine and unshared. I got way
more work done on that machine.
next prev parent reply other threads:[~2024-04-08 15:40 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 ` [TUHS] " Marc Donner
2024-04-08 15:18 ` arnold
2024-04-08 15:29 ` Warner Losh
2024-04-08 15:59 ` Lars Brinkhoff
2024-04-08 15:39 ` Larry McVoy [this message]
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=20240408153958.GL16155@mcvoy.com \
--to=lm@mcvoy.com \
--cc=arnold@skeeve.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).