From: Stephane CHAZELAS <stephane.chazelas@gmail.com>
To: "Stéphane Aulery" <saulery@free.fr>
Cc: 501566@bugs.debian.org, dash@vger.kernel.org
Subject: Re: Bug#501566: [MAN] Clarify two redirection mechanisms
Date: Tue, 9 Dec 2014 16:54:31 +0000 [thread overview]
Message-ID: <20141209165431.GB5708@chaz.gmail.com> (raw)
In-Reply-To: <20141208212203.GA13333@free.fr>
2014-12-08 22:22:03 +0100, Stéphane Aulery:
> Le lundi 08 décembre 2014 à 08:37:38, Stephane CHAZELAS a écrit :
> > 2014-12-08 19:50:05 +0100, Stéphane Aulery:
> > >>>> [n1]>&n2 Redirect standard output (or fd n1) to the same "open
> > >>>> file description" as on fd n2.
> > >>>>
> > >>>> [n1]>&n2 Copy fd n2 as stdout (or fd n1)
[...]
> I wonder more and more if Herbert is willing to accept this tiny patch
> or another. I would not be wasting his time if he does not want or can
> not take care of that. This is free software, there is no obligation.
[...]
What matters here is the mistake fixed in the manual. n>&p has
been around since the end of the 70s. It's unlikely anyone will
learn anything about it from the dash man page.
Let's make it:
[n1]>&n2 Copy file descriptor n2 as stdout (or fd n1)
[n1]<&n2 Copy file descriptor n2 as stdin (or fd n1)
That's more or less the POSIX wording. It may not be as
descriptive as other ones, but I can't imagine anyone
complaining about the correctness or accuracy of it.
--
Stephane
next prev parent reply other threads:[~2014-12-09 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Stephane CHAZELAS [this message]
2014-12-11 6:06 ` Bug#501566: " Herbert Xu
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=20141209165431.GB5708@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=501566@bugs.debian.org \
--cc=dash@vger.kernel.org \
--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