From: Chet Ramey <chet.ramey@case.edu>
To: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] v7 source code for sh
Date: Sun, 20 Feb 2022 17:39:46 -0500 [thread overview]
Message-ID: <615ad728-4a33-29d9-73a9-80f51e35f68e@case.edu> (raw)
In-Reply-To: <efb54745d8b85b76@orthanc.ca>
On 2/20/22 4:19 PM, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
> Chet Ramey writes:
>
>> It always seemed like it would have been just the thing to implement as a
>> tty streams module, but research Unix went in a different direction.
>
> I'm really surprised nobody has implemented a basic readline as a
> tty line discipline by now. I was poking around the OpenBSD NMEA
> line discipline code a few weeks ago and thinking it shouldn't be
> that hard to do.
It's not that hard. The complexity is in how sophisticated you want to get
with redisplay and whether you want to allow user-specified key bindings.
> Did anyone think about doing this in the past? If yes, what made you
> decide against doing it? (Or a streams implementation, for that matter.)
There have been several implementations (I never did one). I suspect that
the people who were in a position to integrate that functionality into
distributed kernels were not supportive, or the code didn't get to them
at the right time.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2022-02-20 22:42 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 17:44 Bakul Shah
2022-02-19 18:44 ` Rob Pike
2022-02-19 19:29 ` Clem Cole
2022-02-19 22:39 ` John Cowan
2022-02-19 23:11 ` Sven Mascheck
2022-02-19 23:34 ` Rob Pike
2022-02-19 23:36 ` silas poulson
2022-02-20 20:54 ` Chet Ramey
2022-02-20 21:02 ` Larry McVoy
2022-02-20 21:19 ` Chet Ramey
2022-02-20 21:19 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-02-20 22:39 ` Chet Ramey [this message]
2022-02-21 1:01 ` Dan Cross
2022-02-22 4:54 ` Dan Stromberg
2022-02-22 5:39 ` Rob Pike
2022-02-22 5:54 ` George Michaelson
-- strict thread matches above, loose matches on Subject: below --
2022-02-22 3:07 Brian Walden
2022-02-22 14:28 ` Chet Ramey
2022-02-22 14:47 ` Clem Cole
2022-02-21 17:58 Norman Wilson
2022-02-21 18:10 ` Rob Pike
2022-02-20 7:24 Rudi Blom
2022-02-19 15:43 Will Senn
2022-02-19 16:03 ` Steve Nickolas
2022-02-19 16:07 ` Clem Cole
2022-02-19 16:43 ` Steve Nickolas
2022-02-19 17:24 ` Ron Natalie
2022-02-19 16:04 ` Clem Cole
2022-02-19 16:06 ` Bakul Shah
2022-02-19 16:57 ` Will Senn
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=615ad728-4a33-29d9-73a9-80f51e35f68e@case.edu \
--to=chet.ramey@case.edu \
--cc=lyndon@orthanc.ca \
--cc=tuhs@minnie.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).