Xref: utzoo alt.sources.d:675 comp.sources.d:5622
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!snorkelwacker!spdcc!ima!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: alt.sources.d,comp.sources.d
Subject: Re: Unnecessary tar-compress-uuencodes
Message-ID: <17089@haddock.ima.isc.com>
Date: 16 Jul 90 18:08:15 GMT
References: <5256@plains.UUCP> <3124@psueea.UUCP> <1990Jul13.161441.8339@druid.uucp> <3131.26a188ca@mccall.com>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Cambridge, MA 02138-5302
Lines: 14

In article <3131.26a188ca@mccall.com> tp@mccall.com writes:
>In article <1990Jul13.161441.8339@druid.uucp>, darcy@druid.uucp (D'Arcy J.M. Cain) writes:
>> Modify shar to [split long lines].  All it would take is to put a '\' if
>> the line goes beyond a certain point and continue on the next line.  The
>> shell will put it back together properly.
>
>Technical question ... Is this true?

No.  Since shar'd files are quoted (via the hack of quoting the word that
identifies the terminator for the here-document), a backslash is not special
there.  You'd have to use an unquoted here-document, and then escape any real
backslashes, dollar signs, or grave accents that appear in the text.

Karl W. Z. Heuer (karl@kelp.ima.isc.com or ima!kelp!karl), The Walking Lint