dash.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stéphane Aulery" <saulery@free.fr>
To: Stephen Shirley <diamond@nonado.net>
Cc: 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:27:19 +0100	[thread overview]
Message-ID: <20141118232718.GA9223@free.fr> (raw)
In-Reply-To: <CAEuPzf47pS0u+uY9-RUjOgGOuuGb6o9htY5Quu-B6dMuOVWA3Q@mail.gmail.com>

Hello Stephen,

Le mardi 11 novembre 2014 à 02:23:21, Stephen Shirley a écrit :
> 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."


Herbert rejected both corrections. Your new proposal is better but
incomplete. Stéphane Chazelas tried to complete it. Moreover you have
not made a new proposal for the first correction.

As I am not dash user, I do not have a good knowledge of the matter. Can
you complete your answer / choice, please?

Thank you in advance for your help.


Original version:

1)  [n1]<&n2    Duplicate standard input (or n1) from file descriptor n2.

2)  [n1]>&n2    Duplicate standard output (or n1) to n2.


Version on Debian bug tracker and refused by H. Xu:

1)  [n1]<&n2    Duplicate standard input (or n1) to file descriptor n2.

2)  [n1]>&n2    Duplicate standard output (or n1) from n2.


Second version of the patch refused by H. Xu:

2)  [n1]>&n2    Redirect standard output (or n1) to n2.


Stéphane Chazelas proposals:

1a) [n1]>&n2    Redirect standard output (or fd n1) to the same "open
                file description" as on fd n2.

1b) [n1]>&n2    Redirect standard output (or fd n1) to
                the same resource as open on fd n2.

1c) [n1]>&n2    Copy fd n2 as stdout (or fd n1)


Regards,

-- 
Stéphane Aulery

  parent reply	other threads:[~2014-11-18 23:29 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       ` Stéphane Aulery [this message]
2014-11-18 23:46         ` Bug#501566: dash: details of redirection/duplication in manpage are reversed 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=20141118232718.GA9223@free.fr \
    --to=saulery@free.fr \
    --cc=501566@bugs.debian.org \
    --cc=dash@vger.kernel.org \
    --cc=diamond@nonado.net \
    /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).