From: Rob Pike <robpike@gmail.com>
To: Richard Salz <rich.salz@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>,
Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Subject: Re: [TUHS] Why does shell write to stderr?
Date: Fri, 8 Apr 2022 08:15:21 +1000 [thread overview]
Message-ID: <CAKzdPgxhEZNihmag-GcDsWLhD1xW9XzO1tYSja=W3kPC=9kGQA@mail.gmail.com> (raw)
In-Reply-To: <CAFH29trish5gf20jUeWv3w3gS_B+frkqAqASg9ZA7jKSgScsdA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
I am indeed a throwback but programs calling stat or stty to examine their
I/O state before deciding how to behave was a shock when I first saw it
done, in Berkeley ls I think, and still feels misguided. I understand the
convenience but not every convenience is good engineering.
-rob
On Fri, Apr 8, 2022 at 7:38 AM Richard Salz <rich.salz@gmail.com> wrote:
> On Thu, Apr 7, 2022 at 5:13 PM Douglas McIlroy <
> douglas.mcilroy@dartmouth.edu> wrote:
>
>> How would you wish to interact with
>> /bin/bash >file
>>
>
> I am not sure. I could see the argument either way right now.
>
>
> On Thu, Apr 7, 2022 at 5:13 PM Douglas McIlroy <
> douglas.mcilroy@dartmouth.edu> wrote:
>
>> How would you wish to interact with
>> /bin/bash >file
>>
>> Doug
>>
>
[-- Attachment #2: Type: text/html, Size: 1695 bytes --]
next prev parent reply other threads:[~2022-04-07 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 21:11 Douglas McIlroy
2022-04-07 21:32 ` Steffen Nurpmeso
2022-04-07 21:36 ` Richard Salz
2022-04-07 22:15 ` Rob Pike [this message]
2022-04-07 22:30 ` George Michaelson
2022-04-07 23:51 ` Rob Pike
2022-04-09 1:46 ` John Cowan
2022-04-09 1:53 ` George Michaelson
2022-04-09 18:05 ` Steffen Nurpmeso
-- strict thread matches above, loose matches on Subject: below --
2022-04-08 9:34 Paul Ruizendaal via TUHS
2022-04-07 17:45 Richard Salz
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='CAKzdPgxhEZNihmag-GcDsWLhD1xW9XzO1tYSja=W3kPC=9kGQA@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=rich.salz@gmail.com \
--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).