From: schily@schily.net (Joerg Schilling)
Subject: [TUHS] etymology of read -u
Date: Tue, 31 May 2016 16:35:57 +0200 [thread overview]
Message-ID: <574da14d.bG9ld/bdPDR6Rj/K%schily@schily.net> (raw)
In-Reply-To: <201605310727.u4V7Rhmp030422@coolidge.cs.Dartmouth.EDU>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
Doug McIlroy <doug at cs.dartmouth.edu> wrote:
> What's the mnmonic significance, if any, of the u in
> the bash builtin read -u for reading from a specified
> file descriptor? Evidently both f and d had already been
> taken in analogy to usage in some other commands.
It seems to be a copy from ksh.
Ksh implements a private "print" builtin that also uses -u fd.
Jörg
--
EMail:joerg at schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'
next prev parent reply other threads:[~2016-05-31 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 7:27 Doug McIlroy
2016-05-31 12:55 ` Chet Ramey
2016-05-31 14:35 ` Joerg Schilling [this message]
[not found] ` <CAEoi9W4YTdJ2bJyAKVQqpd48bTLv7GANrtAK271oXnibuo8v6A@mail.gmail.com>
[not found] ` <CAPz8ZkZjLr1Uj-3VLKK1n5xZq=eeHh+HBeTNHbDVxVTKH+CvCw@mail.gmail.com>
2016-05-31 15:57 ` Dan Cross
2016-05-31 16:49 ` Joerg Schilling
2016-06-01 4:14 Doug McIlroy
2016-06-01 4:17 Doug McIlroy
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=574da14d.bG9ld/bdPDR6Rj/K%schily@schily.net \
--to=schily@schily.net \
/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).