Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site qantel.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!ihnp4!zehntel!dual!qantel!stv
From: stv@qantel.UUCP (Steve Vance@ex2499)
Newsgroups: net.news.group,net.sources.bugs
Subject: Re: Shar files--making leading & trailing stuff into comments
Message-ID: <326@qantel.UUCP>
Date: Tue, 11-Dec-84 16:40:57 EST
Article-I.D.: qantel.326
Posted: Tue Dec 11 16:40:57 1984
Date-Received: Thu, 13-Dec-84 03:18:31 EST
References: <11071@gatech.UUCP> <322@qantel.UUCP>
Reply-To: stv@qantel.UUCP (Steve Vance@ex2499)
Organization: MDS Qantel, Hayward, CA
Lines: 27
Xref: watmath net.news.group:2629 net.sources.bugs:124

In article <322@qantel.UUCP> stv@qantel.UUCP (Steve Vance@ex2499) writes:
> >>--------------- cut here and run the rest through "sh" ---------------
> >
> >It seems to me that if you put colons ":" at the front of all the
> >introductory lines like those above, I could just say "w|sh" to my "rn"
> >prompt...
> >
> 
> From dual!ptsfa!politik!chris Thu Dec  6 21:52:30 1984
> 
> You can always say (in rn) 
> 
>	 | sed 1,/cut/d | sh
> 
> That is easier than going into vi and so on.
> Christopher Seiwald
> dual!ptsfa!politik!chris
 
Hmm, good idea.  Perhaps shar file posters should include the above
suggestion in the descriptive info of shar file postings, eh?

P.S.: I still think that "w|sh" is easier.  
-- 

Steve Vance
{dual,nsc,intelca,proper}!qantel!stv
Qantel Corporation, Hayward, CA