From: Matthias Scheler <tron@zhadum.de>
To: Borzenkov Andrey <Andrej.Borsenkow@mow.siemens.ru>
Cc: zsh-workers@sunsite.dk
Subject: Re: I/O redirection problem in "zsh"
Date: Fri, 25 Oct 2002 13:44:52 +0200 [thread overview]
Message-ID: <20021025114451.GB28474@colwyn.zhadum.de> (raw)
In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B4B6@MOWD019A>
On Fri, Oct 25, 2002 at 03:16:13PM +0400, Borzenkov Andrey wrote:
> This ambiguous. Both > and | mean redirection of stdout.
Is there a better portable way to redirect stderr to the pipe but
ignore stdout?
Kind regards
--
Matthias Scheler http://scheler.de/~matthias/
next prev parent reply other threads:[~2002-10-25 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 10:40 Matthias Scheler
2002-10-25 11:13 ` Oliver Kiddle
2002-10-25 11:16 ` Borzenkov Andrey
2002-10-25 11:44 ` Matthias Scheler [this message]
2002-10-25 12:15 ` Oliver Kiddle
2002-11-06 10:10 ` Zefram
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=20021025114451.GB28474@colwyn.zhadum.de \
--to=tron@zhadum.de \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).