From: Jaap Akkerhuis via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: FD 2
Date: Sun, 22 Jan 2023 11:56:33 +0100 [thread overview]
Message-ID: <ADBDDDAA-1830-46EB-B21C-280EF2A4BEFE@xs4all.nl> (raw)
In-Reply-To: <CAC20D2OfyiNuxtvQGb9wN7a8X4ay_c3aHWBwEdP1MmyVzYi5jA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 573 bytes --]
> On 21 Jan 2023, at 19:27, Clem Cole <clemc@ccc.com> wrote:
>
>
>
> On Sat, Jan 21, 2023 at 12:34 PM Warner Losh <imp@bsdimp.com <mailto:imp@bsdimp.com>> wrote:
>> It looks to be a mixed bag in 5th edition. Cc, ac, comm and find all printf the errors. Diff uses writes to fd 2. I didn't catalog further, but this kinda looks like a developing convention, not yet fully realized. .
> Fair enough and that makes sense...
> ᐧ
I do remember that pr -p actually read from FD 2. It probably still does.
Very useful to align paper in the printer.
jaap
[-- Attachment #1.2: Type: text/html, Size: 1765 bytes --]
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
prev parent reply other threads:[~2023-01-22 10:57 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 22:44 [TUHS] " ron minnich
2023-01-20 22:54 ` [TUHS] " G. Branden Robinson
2023-01-20 22:56 ` Rob Pike
2023-01-20 23:11 ` Larry McVoy
2023-01-20 23:14 ` Rob Pike
2023-01-20 23:22 ` Larry McVoy
2023-01-20 23:13 ` Douglas McIlroy
2023-01-21 3:37 ` Jon Steinhart
2023-01-21 15:42 ` Clem Cole
2023-01-21 17:34 ` Warner Losh
2023-01-21 17:50 ` Warner Losh
2023-01-21 18:26 ` Clem Cole
2023-01-21 18:37 ` Warner Losh
2023-01-22 11:05 ` Jonathan Gray
2023-01-22 21:23 ` Warner Losh
2023-01-22 22:10 ` ron minnich
2023-01-23 7:30 ` arnold
2023-01-23 8:32 ` James Johnston
2023-01-23 8:58 ` G. Branden Robinson
2023-01-23 11:49 ` Brantley Coile
2023-01-23 14:25 ` Ronald Natalie
2023-01-23 17:43 ` Brantley Coile
2023-01-23 16:59 ` Douglas McIlroy
2023-01-24 7:21 ` arnold
2023-01-29 18:51 ` Warner Losh
2023-01-29 19:20 ` Ron Natalie
2023-01-29 20:25 ` Warner Losh
2023-01-30 7:50 ` arnold
2023-01-30 8:09 ` Rob Pike
2023-01-30 15:02 ` Larry McVoy
2023-01-30 15:16 ` Dan Cross
2023-01-30 15:27 ` Larry McVoy
2023-01-30 15:35 ` Dan Cross
2023-01-30 15:45 ` Larry McVoy
2023-01-30 16:09 ` Dan Cross
2023-01-30 16:18 ` Larry McVoy
2023-01-30 19:03 ` Dan Cross
2023-01-30 19:12 ` Brantley Coile
2023-01-30 21:24 ` Larry McVoy
2023-01-30 22:15 ` Rob Pike
2023-01-30 22:50 ` ron minnich
2023-01-30 23:05 ` [TUHS] Child of plan9? (Re: " Bakul Shah
2023-01-31 3:19 ` [TUHS] " Andrew Warkentin
2023-01-30 16:21 ` [TUHS] " Steve Nickolas
2023-01-30 16:27 ` Larry McVoy
2023-01-30 16:32 ` ron minnich
2023-01-30 16:40 ` Clem Cole
2023-01-30 19:55 ` Lawrence Stewart
2023-01-31 21:27 ` Dave Horsfall
2023-01-30 16:48 ` Theodore Ts'o
2023-01-30 16:57 ` Andy Kosela
2023-01-30 17:04 ` Warner Losh
2023-01-30 20:38 ` Theodore Ts'o
2023-01-30 21:01 ` Warner Losh
2023-01-30 21:10 ` Clem Cole
2023-01-30 16:03 ` Bakul Shah
2023-01-30 16:07 ` Larry McVoy
2023-01-30 16:13 ` Bakul Shah
2023-01-30 16:22 ` Steve Nickolas
2023-01-30 16:17 ` Dan Cross
2023-01-30 16:18 ` Ralph Corderoy
2023-01-30 16:41 ` [TUHS] job control (Re: " Bakul Shah
2023-01-30 19:07 ` [TUHS] " Dan Cross
2023-01-30 13:26 ` John Cowan
2023-01-30 14:30 ` arnold
2023-01-30 0:25 ` Phil Budne
2023-01-30 2:08 ` Warner Losh
2023-01-21 18:27 ` Clem Cole
2023-01-22 10:56 ` Jaap Akkerhuis via TUHS [this message]
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=ADBDDDAA-1830-46EB-B21C-280EF2A4BEFE@xs4all.nl \
--to=tuhs@tuhs.org \
--cc=jaapna@xs4all.nl \
/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).