BL>          I'm still writing my VB pkt twitter, and it occurred to me
 BL> that I could twit Rod more efficiently by identifying his packet and
 BL> leaving it out of pktjoin.

 BL>   The packets you send me seem to be all from one person or the other.
 BL> Will this always be so?

It's not guaranteed to always be so, but the way I run my system,
it is very unlikely that it won't be so.

 BL>   BTW, that error in pktjoin is a bastard.

 BL>   If you tell it to "pktjoin *.pkt tenmin.pkt" it gets
right up itself
 BL> by joining tenmin.pkt and doubles itself, but I don't see why pwk2qwk
 
You and others can call it an "error" or a "bug", but it is a 
documented (in the source code) restriction, ever since Day 1. 
 
 BL> would barf on that. Isn't one packet the same as another? You'd only
 BL> get dupes. The doubled packet I looked at seemed okay.

By not following the documentation (in the source code), you are
going to get unpredictable results.  And no, I can't predict 
what they are, either.  It will be attempting to process a
half-written packet, which doesn't conform to standards because
it hasn't been written yet.  BFN.  Paul.
@EOT:

--- Mksmsg