From: Stephen Shirley <diamond@nonado.net>
To: "Stéphane Aulery" <saulery@free.fr>, 501566-quiet@bugs.debian.org
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
dash@vger.kernel.org, 501566@bugs.debian.org,
501566-submitter@bugs.debian.org
Subject: Re: Bug#501566: dash: details of redirection/duplication in manpage are reversed
Date: Tue, 11 Nov 2014 14:23:21 +0100 [thread overview]
Message-ID: <CAEuPzf47pS0u+uY9-RUjOgGOuuGb6o9htY5Quu-B6dMuOVWA3Q@mail.gmail.com> (raw)
In-Reply-To: <20141110134957.GA5664@free.fr>
Hi,
On 10 November 2014 14:49, Stéphane Aulery <saulery@free.fr> wrote:
> Le lundi 10 novembre 2014 à 09:24:09, Herbert Xu a écrit :
>> Stéphane Aulery <saulery@free.fr> wrote:
>> >
>> > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501566
>> >
>>
>> I'm sorry but this patch looks wrong and the text looks correct
>> to me as is.
>
> Ok. I passed the information but I'm not really able to judge its
> pertinence. In this case I close this bug.
So, i finally managed to figure out what the problem is. The wording
is ambiguous (or maybe just insufficiently clear).
"[n1]>&n2 Duplicate standard output (or n1) to n2."
How i read it (6 years ago :P) was that meant dup2(n1, n2), because
the only actual /duplication/ is of file descriptors. I've just
realised that the intended meaning is "redirect n1 to where n2 is
currently", i.e. dup2(n2, n1), as expected. Can i suggest a simple
fix:
"[n1]>&n2 Redirect standard output (or n1) to n2."
It doesn't cover the case where n2 is later changed, and how n1 does
not follow this, but it's the simplest fix i see.
Steve
--
"You are technically correct, the best kind of correct."
- Bureaucrat 1.0, Futurama
next prev parent reply other threads:[~2014-11-11 13:23 UTC|newest]
Thread overview: 17+ 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 ` Stephen Shirley [this message]
2014-11-11 14:19 ` Bug#501566: " 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
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
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=CAEuPzf47pS0u+uY9-RUjOgGOuuGb6o9htY5Quu-B6dMuOVWA3Q@mail.gmail.com \
--to=diamond@nonado.net \
--cc=501566-quiet@bugs.debian.org \
--cc=501566-submitter@bugs.debian.org \
--cc=501566@bugs.debian.org \
--cc=dash@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=saulery@free.fr \
/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).