From: mhw@minster.york.ac.uk (Mark H. Wilkinson)
To: Steve_Kilbane@cegelecproj.co.uk (Steve_Kilbane),
sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: sam's pipe
Date: Thu, 20 Apr 1995 18:09:35 -0400 [thread overview]
Message-ID: <swordfish.798424307@minster.york.ac.uk> (raw)
In-Reply-To: Steve_Kilbane's message, dated Apr 20, 1:20pm
Steve_Kilbane wrote:
> Subject: sam's pipe
>
> Does anyone actually use sam's input pipe, apart from with
> the B command?
I've been using this rc function for a while:
fn mk {
if (test -f Errors) {
builtin mk $* |[2] tee Errors
test -s Errors && { { echo b Errors ; echo e } | samsend }
} else {
builtin mk $*
}
}
samsend is a stripped-down version of B which sends stdin to the pipe,
rsh'ing to a remote machine if necessary to avoid NFS problems. I also
have scripts to do B, D and cd operations from rc using samsend.
-Mark.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Mark H. Wilkinson <mhw@minster.york.ac.uk> : Research student in user
University of York, England : interface management systems
next reply other threads:[~1995-04-21 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-04-20 22:09 Mark H. Wilkinson [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-04-20 17:20 Steve_Kilbane
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=swordfish.798424307@minster.york.ac.uk \
--to=mhw@minster.york.ac.uk \
--cc=Steve_Kilbane@cegelecproj.co.uk \
--cc=sam-fans@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).