From: "Stéphane CHAZELAS" <stephane.chazelas@gmail.com>
To: "Stéphane Aulery" <saulery@free.fr>
Cc: Stephen Shirley <diamond@nonado.net>,
Herbert Xu <herbert@gondor.apana.org.au>,
501566@bugs.debian.org, dash@vger.kernel.org
Subject: Re: Bug#501566: dash: details of redirection/duplication in manpage are reversed
Date: Wed, 19 Nov 2014 00:00:08 +0000 [thread overview]
Message-ID: <20141119000008.GC3963@chaz.gmail.com> (raw)
In-Reply-To: <20141118234603.GA9586@free.fr>
2014-11-19 00:46:03 +0100, Stéphane Aulery:
> Hello Stephen and Herbert,
>
> Stéphane Chazelas just made a complete proposal:
>
>
> 1) [n1]<&n2 Redirect standard input (or fd n1) from the same
> resource as open on fd n2.
>
> 2b) [n1]>&n2 Redirect standard output (or fd n1) to
> the same resource as open on fd n2.
>
>
> What do you think about?
[...]
A final touch (add "currently").
[n1]<&n2 Redirect standard input (or fd n1) from the same
resource as currently open on fd n2.
[n1]>&n2 Redirect standard output (or fd n1) to
the same resource as currently open on fd n2.
--
Stephane
prev parent reply other threads:[~2014-11-19 0:00 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
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 [this message]
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=20141119000008.GC3963@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=501566@bugs.debian.org \
--cc=dash@vger.kernel.org \
--cc=diamond@nonado.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.