From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: pipes
Date: Thu, 11 Jun 1992 23:53:11 -0400 [thread overview]
Message-ID: <92Jun11.235317edt.2538@groucho.cs.psu.edu> (raw)
So is this useful?
; cat |
ls
file1 file2 file3
How about this?
; cat |[3=4] |[4=5] cat
(It would be nice to get two pipes connecting the cats?) The null
command doesn't seem well defined to me.
reply other threads:[~1992-06-12 3:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=92Jun11.235317edt.2538@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--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).