From: don@DonHopkins.com (Don Hopkins)
Subject: stty erase '^?' in v7
Date: Sun, 15 Oct 2017 15:10:26 +0200 [thread overview]
Message-ID: <6C18EDF4-7532-4C56-B566-D1C1A0C0A81C@gmail.com> (raw)
In-Reply-To: <B12F2924-0495-4DB8-BA00-2B529DA03EE3@ronnatalie.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
I loved ^T on Unix! I remember when somebody at UMCP added that feature to our 4.2 BSD Vax mimsy. The early version had the fun side-effect of being unregulated. Who added the one-second delay between responding to ^T so you couldn’t any longer hold down ^T with auto-repeat to drive the CPU load through the ceiling and watch as it got higher and higher trying to respond to all those ^T's? (Does that qualify as a Heizenbug, or is that a denial of self service?)
-Don
> On 14 Oct 2017, at 16:44, Ronald Natalie <ron at ronnatalie.com> wrote:
>
> When Mike Muuss was working on the scheduler he added the ^T ala TENEX process list. What was displayed changed over time. I think I finally moved a “snippet” of the arg list over from the user structure to the proc structure so ^T would be able to get it.
>
next prev parent reply other threads:[~2017-10-15 13:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 12:52 Noel Chiappa
2017-10-14 14:40 ` Clem Cole
2017-10-14 14:44 ` Ronald Natalie
2017-10-15 13:10 ` Don Hopkins [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-15 14:39 Noel Chiappa
2017-10-14 4:25 Noel Chiappa
2017-10-14 4:48 ` Will Senn
2017-10-14 6:31 ` Dave Horsfall
2017-10-14 14:03 ` Will Senn
2017-10-14 22:01 ` Dave Horsfall
2017-10-14 2:59 Will Senn
2017-10-14 4:08 ` Grant Taylor
2017-10-14 4:39 ` Random832
2017-10-14 5:03 ` Will Senn
2017-10-16 14:46 ` Random832
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=6C18EDF4-7532-4C56-B566-D1C1A0C0A81C@gmail.com \
--to=don@donhopkins.com \
/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).