From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: John Cowan <cowan@ccil.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Why does shell write to stderr?
Date: Sat, 09 Apr 2022 20:05:05 +0200 [thread overview]
Message-ID: <20220409180505.bKC2a%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAD2gp_RsFWGUtj-9QDKSG3h8Otxb0ZY5M7G00ZAjV=dKEg+Rsw@mail.gmail.com>
John Cowan wrote in
<CAD2gp_RsFWGUtj-9QDKSG3h8Otxb0ZY5M7G00ZAjV=dKEg+Rsw@mail.gmail.com>:
|On Thu, Apr 7, 2022 at 7:53 PM Rob Pike <robpike@gmail.com> wrote:
|If you never ring the bell in the editor, the issue never comes up, the
|> code is simpler, and there's less to understand.
|
|Well, yes. And by the same token, you can eliminate the complexities of
|i18n by having only one diagnostic, namely "?" (or by pretending all the
|world is anglophone).
|
|But setting aside for the moment this style of argumentation, let's
|consider directory colorization. I have no dog in this fight, as I set all
|my terminals to black-on-white as God and Gutenberg intended, and set TERM
Johannes Gutenberg? The bible was in parts red-on-white at least,
and had beautiful coloured paintings, too. (They did not know
about the communist Charlie Chaplin and his Modern Times by then.)
...
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2022-04-09 18:07 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
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 [this message]
-- 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=20220409180505.bKC2a%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=cowan@ccil.org \
--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).