From: Atom 'Smasher' <atom@suspicious.org>
To: zsh-users@sunsite.dk
Subject: command1 >>(command2)
Date: Mon, 20 Sep 2004 05:44:50 -0400 (EDT) [thread overview]
Message-ID: <20040920053918.L344@willy_wonka> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
where is this documented?
command1 >>(command2)
i've found that it's useful for duplicating stdout into multiple commands:
command1 >>(command2) >>(command3)
{ echo X ; echo Y ; } >>(egrep X) >>(egrep -v X)
but there doesn't seem to be any control over whether command2 or command3
finishes first. in the above example it ~usually~ outputs X then Y, but
sometimes Y then X. is there any way to control this?
thanks...
...atom
_________________________________________
PGP key - http://atom.smasher.org/pgp.txt
762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
-------------------------------------------------
fascism: n. A system of government that exercises a dictatorship
of the extreme right, typically through the merging of state and
business leadership, together with belligerent nationalism.
-- The American Heritage Dictionary, 1983
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.6 (FreeBSD)
Comment: What is this gibberish?
Comment: http://atom.smasher.org/links/#digital_signatures
iQEcBAEBCAAGBQJBTqaYAAoJEAx/d+cTpVci/k8IAKeeN5Rq4d1Pk0rB0LG8gU3u
BXImuMPvRf/fHkhMJvwRY+0bEBLhtfR0VCrc9Ush2nrLRyZBCF1sjk2LxPGCjogj
AL7Ferbhfng2lqUffO3ZCy+Qqe5t0o7IEn5msgSYxODNbqEZszZVA15eIZ4h0Pxv
ZQVoPFlmWnXjM46lxqSndch0W7jLUyJukjD2eUJG3mmLrYfsOenSlFWfjicPZo+c
WorP4ZCtPwdRfb0g/nELfsKPeJSZiQ6q87kZTfgwQJxchc/pr3Ch218aSGZg2W83
lDBpEGklQJfgwb190RuU0PupCH7dSWMW2iYHkugPb71TZ4B8o1Hrl2nMEiRjSKA=
=SZ6/
-----END PGP SIGNATURE-----
next reply other threads:[~2004-09-20 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 9:44 Atom 'Smasher' [this message]
2004-09-20 16:08 ` Bart Schaefer
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=20040920053918.L344@willy_wonka \
--to=atom@suspicious.org \
--cc=zsh-users@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).