From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from minster.york.ac.uk ([144.32.128.41]) by hawkwind.utcs.utoronto.ca with SMTP id <24105>; Thu, 20 Apr 1995 20:31:54 -0400 Message-ID: From: mhw@minster.york.ac.uk (Mark H. Wilkinson) Date: Thu, 20 Apr 1995 18:09:35 -0400 In-Reply-To: Steve_Kilbane's message, dated Apr 20, 1:20pm X-Face: Bsp[Ds(Y#/{==j:Cv'"IK4R^D0_z]{'OYtp2^EYqpG)88CsdBm&LJ{idLZWx}AKf}E4#|@4DT4cX3 ?!>aIVcxmd#1 X-Url: http://Dcpu1.cs.york.ac.uk:6666/mhw/ X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Steve_Kilbane@cegelecproj.co.uk (Steve_Kilbane), sam-fans@hawkwind.utcs.toronto.edu Subject: Re: sam's pipe 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 : Research student in user University of York, England : interface management systems