ST 'shar' file coding

Article View: comp.sys.atari.st

Article #26496

#26496

From: Paul Smee
Date: Fri, 24 Apr 1987 16:01

13 lines
1224 bytes

Could I suggest that the ascii TAB character not be used when packing
shar files for distribution?  The problem is that at least along some
routes, systems change them into the 'right' number of spaces.  (There's
universal disagreement as to what 'right' means, which is yet another
problem, but...)

So, what happens is that I get files for which the 'sed' line of the
unpacker is looking for /^<2-SPACES>X/, while the actual packed lines
begin /^<8-SPACES>X/  (or maybe 10-SPACES, or ...).  The amount of hand-fixing
required almost negates the advantages of using shar for the unpacking.
If /^X/ isn't enough, then how about something unlikely like /^XXX/ which
wouldn't exhibit the problem?

Technical Details

Message-ID: <1021@bath63.ux63.bath.ac.uk>

Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!mcvax!ukc!dcl-cs!bath63!pes

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!mcvax!ukc!dcl-cs!bath63!pes
From: pes@ux63.bath.ac.uk (Paul Smee)
Newsgroups: comp.sys.atari.st
Subject: ST 'shar' file coding
Message-ID: <1021@bath63.ux63.bath.ac.uk>
Date: Fri, 24-Apr-87 12:01:01 EDT
Article-I.D.: bath63.1021
Posted: Fri Apr 24 12:01:01 1987
Date-Received: Sun, 26-Apr-87 04:43:29 EDT
Reply-To: pes@ux63.bath.ac.uk (Paul Smee)
Distribution: world
Organization: AUCC c/o University of Bath
Lines: 13