From: Steve Nickolas <usotsuki@buric.co>
To: arnold@skeeve.com
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] 8th Edition and /dev/stdio
Date: Wed, 22 Apr 2020 05:35:42 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.2004220534560.35252@frieza.hoshinet.org> (raw)
In-Reply-To: <202004220933.03M9XWk2002533@freefriends.org>
On Wed, 22 Apr 2020, arnold@skeeve.com wrote:
> Other mail in the thread credits Tom Duff with /dev/fd ... In any case,
> /dev/stdin et al was a great idea.
I make *heavy* use of /dev/stdin and /dev/stdout on Linux. Very useful
concept.
-uso.
next prev parent reply other threads:[~2020-04-22 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 13:59 Paul Ruizendaal
2020-04-20 14:28 ` arnold
2020-04-20 15:01 ` Paul Ruizendaal
2020-04-20 15:16 ` arnold
2020-04-20 17:58 ` Paul Ruizendaal
2020-04-20 18:17 ` Derek Fawcus
2020-04-20 18:32 ` arnold
2020-04-22 9:21 ` Rob Pike
2020-04-22 9:33 ` arnold
2020-04-22 9:35 ` Steve Nickolas [this message]
2020-04-22 9:41 ` Rob Pike
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=alpine.BSF.2.02.2004220534560.35252@frieza.hoshinet.org \
--to=usotsuki@buric.co \
--cc=arnold@skeeve.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).