Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site utah-cs.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!genrad!wjh12!talcott!harvard!seismo!utah-cs!lepreau From: lepreau@utah-cs.UUCP (Jay Lepreau) Newsgroups: net.micro.mac Subject: Re: desk top stuff (and other "shar" "binhex") Message-ID: <3153@utah-cs.UUCP> Date: Sun, 16-Dec-84 08:50:43 EST Article-I.D.: utah-cs.3153 Posted: Sun Dec 16 08:50:43 1984 Date-Received: Tue, 18-Dec-84 03:26:42 EST References: <546@oddjob.UChicago.UUCP> <18142@lanl.ARPA> Reply-To: lepreau@utah-cs.UUCP (Jay lepreau) Organization: Univ of Utah CS Dept Lines: 16 Summary: In article <18142@lanl.ARPA> dlc@lanl.ARPA warns people not to use shar format because the source can get munged due to sh interpretation. If you do it right, this will never happen. The proper way is to quote the sh's "here documents" (whazzat, you say). Examples: This works, keeping $ signs and such intact: sed 's/^X//' >foo << 'FUNNYEOF' ... FUNNYEOF So does this: sed 's/^X//' >foo << \FUNNYEOF This does not: sed 's/^X//' >foo << FUNNYEOF This is actually documented in sh(1). Also, you must run these thru sh, not csh. So please keep using shar format.