Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site lanl.ARPA
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!genrad!wjh12!talcott!harvard!seismo!cmcl2!lanl!dlc
From: dlc@lanl.ARPA
Newsgroups: net.micro.mac
Subject: Re: desk top stuff (and other "shar" "binhex")
Message-ID: <18142@lanl.ARPA>
Date: Sun, 16-Dec-84 02:17:47 EST
Article-I.D.: lanl.18142
Posted: Sun Dec 16 02:17:47 1984
Date-Received: Tue, 18-Dec-84 03:25:21 EST
References: <546@oddjob.UChicago.UUCP>
Sender: newsreader@lanl.ARPA
Organization: Los Alamos National Laboratory
Lines: 13

A note to anyone who sends or get binhex (the new, compressed format) files
in a "shar" file.  The Bourne shell, which processes "shar" archives, likes
to do special things with dollar signs and also reverse slashes at the end
of a line, both of which occur frequently in binhex files.  So, since I sent
the first "shar" file with a "binhex" file in it, you are forewarned.  Once
I received a file instead of sending one, I immediately saw the problem --
every coincidental "$$" had disappeared, and the process id for the shell
appeared in its place, and one line was twice as long as the others.  I'd
say the best policy for the future is to send binhex files in separate news
articles, no "shar" involved.

This may be why some of you had problems with the new binhex in the first
place, if you started from Microsoft BASIC.