From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Cc: sbeck@cise.ufl.edu
Subject: Re: Bug report + feature request
Date: Fri, 6 Oct 2000 10:24:27 +0200 (MET DST) [thread overview]
Message-ID: <200010060824.KAA14552@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Sullivan N. Beck"'s message of Thu, 05 Oct 2000 14:11:21 -0400
Sullivan N. Beck wrote:
> ...
>
> Now for the feature request. Since I'd actually like to separate and
> pipe STDOUT and STDERR separately to different commands (all of the
> above came about from various attempts to get this working) without
> resorting to fifos, intermediate files, etc., what I'd _really_ like to
> do is to be able to pipe different file descriptors similar to how I can
> redirect them to a file. For example, I'd like to replace the following
> lines:
>
> COMMAND > /tmp/stdout 2> /tmp/stderr
> cat /tmp/stderr | STDERR_COMMAND
> cat /tmp/stdout | STDOUT_COMMAND
>
> with the single line:
>
> COMMAND >| STDOUT_COMMAND 2>| STDERR_COMMAND
>
> If this syntax isn't acceptable, that's fine with me. Any syntax is
> fine. I'd just like the functionality.
How should it find out if, in your example, STDERR_COMMAND should be
used for COMMAND or STDOUT_COMMAND?
But anyway... have you seen the >>(cmd) process substitution?
You can do:
COMMAND >>(STDOUT_COMMAND) 2>>(STDERR_COMMAND)
or
COMAMND 2>>(STDERR_COMMAND) | STDOUT_COMMAND
if you prefer.
Note to workers: in the info file, >>(foo) is shown as `> >(foo)'. Urgh.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-10-06 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-06 8:24 Sven Wischnowsky [this message]
2000-10-08 1:14 ` Process substitution Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-10-05 18:11 Bug report + feature request Sullivan N. Beck
2000-10-05 18:32 ` Peter Stephenson
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=200010060824.KAA14552@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=sbeck@cise.ufl.edu \
--cc=zsh-workers@sunsite.auc.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).