From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: dash@vger.kernel.org
Subject: Re: [MAN] Clarify two redirection mechanisms
Date: Mon, 1 Dec 2014 12:27:19 +0000 [thread overview]
Message-ID: <20141201122718.GC3842@chaz.gmail.com> (raw)
In-Reply-To: <20141201100456.GA16404@gondor.apana.org.au>
2014-12-01 18:04:56 +0800, Herbert Xu:
[...]
> > --- a/src/dash.1
> > +++ b/src/dash.1
> > @@ -402,11 +402,13 @@ Append standard output (or n) to file.
> > .It [n] Ns \*[Lt] file
> > Redirect standard input (or n) from file.
> > .It [n1] Ns \*[Lt]& Ns n2
> > -Duplicate standard input (or n1) from file descriptor n2.
> > +Redirect standard input (or fd n1) from the same resource as currently open on
> > +fd n2.
>
> "Resource" is rather unwieldy, how about simply "file"?
[...]
"file" could be misleading (as actually it's dup(2)ing a file
descriptor, so more like redirecting to same _open file
description_ (not the same as reopening the file like "n1>
/dev/fd/n2" does on Linux for instance) and "file" is understood
by many as "regular file" while here, it could be (and often is)
socket/pipe/devices...).
IMO, "resource" is vague enough so as not to give the wrong idea
and I like that wording because it conveys the intended
mechanism clearly ("redirect to same thing as"). But I agree
it's not ideal.
The "dupliciting fd x onto y" wording may be more correct, but
doesn't convey the redirection idea as clearly IMO.
--
Stephane
next prev parent reply other threads:[~2014-12-01 12:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 11:19 dash: details of redirection/duplication in manpage are reversed Stéphane Aulery
2014-11-10 13:24 ` Herbert Xu
2014-11-10 13:49 ` Stéphane Aulery
2014-11-11 13:23 ` Bug#501566: " Stephen Shirley
2014-11-11 14:19 ` Stephane Chazelas
2014-11-12 2:13 ` Herbert Xu
2014-11-11 15:08 ` Herbert Xu
2014-11-11 20:46 ` Stéphane Aulery
2014-11-11 20:47 ` Stéphane Aulery
2014-11-12 2:12 ` Herbert Xu
2014-11-12 11:09 ` Stéphane Aulery
2014-11-21 11:52 ` [MAN] Clarify two redirection mechanisms saulery
2014-12-01 10:04 ` Herbert Xu
2014-12-01 12:27 ` Stephane Chazelas [this message]
2014-11-18 23:27 ` Bug#501566: dash: details of redirection/duplication in manpage are reversed Stéphane Aulery
2014-11-18 23:46 ` Stéphane Aulery
2014-11-19 0:00 ` Stéphane CHAZELAS
2014-12-08 18:50 Bug#501566: [MAN] Clarify two redirection mechanisms Stéphane Aulery
2014-12-08 20:37 ` Stephane CHAZELAS
2014-12-08 21:22 ` Stéphane Aulery
2014-12-08 21:56 ` Jonathan Nieder
2014-12-08 22:15 ` Stéphane Aulery
2014-12-09 16:54 Bug#501566: " Stephane CHAZELAS
2014-12-11 9:03 ` saulery
2014-12-25 22:51 ` Herbert Xu
2014-12-26 11:35 ` Stéphane Aulery
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=20141201122718.GC3842@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=dash@vger.kernel.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).