From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3/2) with ESMTP id AAA18460 for ; Sat, 20 Jul 1996 00:40:33 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id KAA20024; Fri, 19 Jul 1996 10:35:13 -0400 (EDT) Resent-Date: Fri, 19 Jul 1996 10:35:13 -0400 (EDT) From: Zefram Message-Id: <11608.199607191434@stone.dcs.warwick.ac.uk> Subject: Re: Zefram's FUNCTIONARGZERO and SHFILESUBST patches To: schaefer@nbn.com Date: Fri, 19 Jul 1996 15:34:08 +0100 (BST) Cc: zsh-workers@math.gatech.edu In-Reply-To: <9607181738.ZM14804@candle.brasslantern.com> from "Bart Schaefer" at Jul 18, 96 05:38:56 pm X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]7833.03 X-US-Congress: Moronic fuckers MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"-I-BN.0.pu4.Wqvxn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/1715 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >By the way, how many MIME-unaware mail readers do we have on >this list? As an author of email software, it kinda bugs me >to be sending a uuencoded block in my message text rather than >using the nifty MIME body part capabilities of my user agent. We can probably all handle MIME, but in my case it involves manually stripping out the bare base64-encoded data and running it through a perl script. I'd much rather use uuencode. -zefram