From: Dan Cross <crossd@gmail.com>
To: Chester Ramey <chet.ramey@case.edu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] v7 source code for sh
Date: Sun, 20 Feb 2022 20:01:12 -0500 [thread overview]
Message-ID: <CAEoi9W6Y29yEzdYjSOpHhWWm+Dtb6Bm9EVhDMcfje6i3Pcu+dw@mail.gmail.com> (raw)
In-Reply-To: <615ad728-4a33-29d9-73a9-80f51e35f68e@case.edu>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
On Sun, Feb 20, 2022 at 5:42 PM Chet Ramey <chet.ramey@case.edu> wrote:
> On 2/20/22 4:19 PM, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
> > 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.
>
At this point, it feels like the die has been cast. Readline, or something
like it, is "good enough" and those working with something plan9-like don't
need the functionality at all. Arguably, on Unix-style systems it would be
cleaner to do in the kernel, but aside from aesthetics, what's the
incentive to change?
- Dan C.
[-- Attachment #2: Type: text/html, Size: 1242 bytes --]
next prev parent reply other threads:[~2022-02-21 1:04 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
2022-02-21 1:01 ` Dan Cross [this message]
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=CAEoi9W6Y29yEzdYjSOpHhWWm+Dtb6Bm9EVhDMcfje6i3Pcu+dw@mail.gmail.com \
--to=crossd@gmail.com \
--cc=chet.ramey@case.edu \
--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).