From: Amos Shapir amos@CS.HUJI.AC.IL
Subject: An rc challenge
Date: Mon, 27 Mar 1995 08:39:23 -0500 [thread overview]
Message-ID: <19950327133923.VGRWqip0scuNpUvqA67q612p3v_YwHqEL3Ef8JhKu3s@z> (raw)
How to do spliced pipes:
cmd_a > file; cmd_b <{ cmd_c < file} <{ cmd_d < file }
can also be done as:
cmd_b <{ cmd_a | cmd_c} <{ cmd_a | cmd_d }
But if "cmd_a" is heavy, how can this be done without running it
twice, or using a temporary file?
Alternatively, is there an easy way to do named pipes in rc?
Thanks,
Amos Shapir Net: amos@cs.huji.ac.il
Paper: The Hebrew Univ. of Jerusalem, Dept. of Comp. Science.
Givat-Ram, Jerusalem 91904, Israel
Tel: +972 2 585706,586950 GEO: 35 11 46 E / 31 46 21 N
next reply other threads:[~1995-03-27 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-03-27 13:39 Amos [this message]
1995-03-30 7:07 Amos
1995-03-30 7:40 philw
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=19950327133923.VGRWqip0scuNpUvqA67q612p3v_YwHqEL3Ef8JhKu3s@z \
--to=9fans@9fans.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).