Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!sun!quintus!ok
From: ok@quintus.uucp (Richard A. O'Keefe)
Newsgroups: comp.sources.wanted
Subject: Re: "Safe" unshar
Message-ID: <781@quintus.UUCP>
Date: 30 Nov 88 13:14:12 GMT
References: <440@rhesus.primate.wisc.edu> <346@lakart.UUCP>
Sender: news@quintus.UUCP
Reply-To: ok@quintus.UUCP (Richard A. O'Keefe)
Organization: Quintus Computer Systems, Inc.
Lines: 15

In article <346@lakart.UUCP> dg@lakart.UUCP (David Goodenough) writes:
>What it does, is to look for lines of the form:
>
>sed 's/^X//' > file.xyz << FunkyStuff
>
>get the ^X, file.xyz and FunkyStuff out, open file.xyz for output,
>read the input shar till it finds a line FunkyStuff, and trim X off the

It might be a good idea to be a wee bit more flexible.  Not everyone uses
StuffyFunk.  (The sharchiver I have uses lines like
	sed -e 's/^X//' >file <<'------ EOF ------'
and I have considered changing it to use
	<<'------ EOF ------' sed -e 's/^X//' >file
so that the variable part of the line would always start at a fixed column.
I've noticed several other end-of-file markers in use on the net.