Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!marque!lakesys!mikes
From: mikes@lakesys.UUCP (Mike Shawaluk)
Newsgroups: comp.sys.amiga
Subject: Re: Simple questions about moderated groups and Bridgeboard
Summary: Use pipes!
Keywords: No Flames! Ill-tempered developers please ignore!
Message-ID: <604@lakesys.UUCP>
Date: 6 May 89 11:27:25 GMT
References: <6526@homxc.ATT.COM> <8750@xanth.cs.odu.edu>
Reply-To: mikes@lakesys.UUCP (Mike Shawaluk)
Organization: Lake Systems - Milwaukee, Wisconsin
Lines: 28

In article <8750@xanth.cs.odu.edu> tadguy@cs.odu.edu (Tad Guy) writes:
>xanth% cat joe.zu? > tmp
> ...
>xanth% uudecode tmp

Of course, the true UN*X hacker/enthusiast would have combined these two
operations into one step via piping, and would have saved themselves the
bother of deleting the temporary file later; vis:

whatever% cat joe.zu? | uudecode

At least I know that this works for the version of uudecode that we have
here.

Oh, and by the way, in case there's ever a multi-part posting with more than
9 parts (there was one last year, but happily that type of thing hasn't been
going on lately), you'd use a command of the form:

whatever% cat bob.zu? bob.zu1? | uudecode

assuming that there were no more than 19 parts, and the the files were named
with .zu1, .zu2, ... .zu9, .zu10, etc. (which is how they were named last
time, instead of the slightly more easily sortable .zu01, ...)

-- 
   - Mike Shawaluk 
       (mikes@lakesys.lakesys.com  OR  ...!uunet!marque!lakesys!mikes)
    "Where were you on the night of August 12?"