From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: dash@vger.kernel.org
Subject: Re: Bug#501566: dash: details of redirection/duplication in manpage are reversed
Date: Tue, 11 Nov 2014 14:19:11 +0000 [thread overview]
Message-ID: <20141111141911.GC4343@chaz.gmail.com> (raw)
In-Reply-To: <CAEuPzf47pS0u+uY9-RUjOgGOuuGb6o9htY5Quu-B6dMuOVWA3Q@mail.gmail.com>
2014-11-11 14:23:21 +0100, Stephen Shirley:
[...]
> "[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.
[...]
That's ambiguous.
Maybe:
[n1]>&n2 Redirect standard output (or fd n1) to the same "open
file description" as on fd n2.
[n1]>&n2 Redirect standard output (or fd n1) to the same
resource as open on fd n2.
[n1]>&n2 Copy fd n2 as stdout (or fd n1)
?
--
Stephane
next prev parent reply other threads:[~2014-11-11 14:20 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 ` Bug#501566: " Stephen Shirley
2014-11-11 14:19 ` Stephane Chazelas [this message]
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=20141111141911.GC4343@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).