From: malte@techfak.uni-bielefeld.de
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: Question about redirection
Date: Thu, 16 Jul 1992 06:13:37 -0400 [thread overview]
Message-ID: <9207161013.AA00612@dahlie.techfak.uni-bielefeld.de> (raw)
In-Reply-To: Mail from 'jutta@cs.tu-berlin.de' dated: Thu, 16 Jul 92 2:02:48 MET DST
I'm sorry for not being precise with my question. What I want to know
is why
{ echo stderr >[1=2]; echo stdout } >[2=1] > /dev/null
and
{ echo stderr >[1=2]; echo stdout } |[2=1] cat > /dev/null
although lexically similar, differ in their semantics, while
{ echo stderr >[1=2]; echo stdout } |[2=1] cat > /dev/null
and
{ echo stderr >[1=2]; echo stdout } >[2] /dev/null
look quite different, but are semantically equal. I became aware of this when
I was asked about something similar by a beginner. I feel it is hard to
explain why >[n=m] differs from |[n=m].
Malte.
next reply other threads:[~1992-07-16 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-07-16 10:13 malte [this message]
1992-07-16 16:18 ` Scott Schwartz
1992-07-21 0:45 ` John Mackin
1992-07-21 2:06 ` Scott Schwartz
-- strict thread matches above, loose matches on Subject: below --
1992-07-15 10:44 malte
1992-07-15 11:00 ` Tim.Goodwin
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=9207161013.AA00612@dahlie.techfak.uni-bielefeld.de \
--to=malte@techfak.uni-bielefeld.de \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).