From: Will Senn <will.senn@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Traditional method of dealing with embedded shar files
Date: Fri, 24 Jul 2020 14:21:31 -0500 [thread overview]
Message-ID: <28e558bd-d047-9a13-09d2-638df537a915@gmail.com> (raw)
In-Reply-To: <CAC20D2NoJga2oi90wmDSrxReDYMfxxhX76fpOeSA_LVGNFoQdA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]
On 7/24/20 1:57 PM, Clem Cole wrote:
>
>
> On Fri, Jul 24, 2020 at 2:47 PM Will Senn <will.senn@gmail.com
> <mailto:will.senn@gmail.com>> wrote:
>
>> I'm just getting comfortable using sed, thanks for the
>> simplification.
>
> The issue with sed is that different shar programs used different
> cut/here markers. Using vi was safer and as I said, since you did not
> do it everyday, it was no big deal.
> Maybe since you have a number of these you want to apply, check with a
> grep for the expected marker before you try to apply the sed script
> and only do it in a more automated matter catching the vast majority
> of the markers.]
>
> You asked how we did it. As was said, there were a number of
> unshar(1) commands out there, that did the sed for you. Go looking in
> the archives, but generally speaking using vi was 'good enough' for
> day to day work because you did not run it that often / every day /
> were >>usually<< not apply a lot of them in a row.
>
> Clem
Yup, I was curious what it looked like in the day. After hearing from
everybody, I will use vi the first time and if I have to do it a bunch
of ties, will test a sed script... or just wait 'til Warner's done and
just check it from source code :).
Will
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
[-- Attachment #2: Type: text/html, Size: 3590 bytes --]
next prev parent reply other threads:[~2020-07-24 19:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 17:23 Will Senn
2020-07-20 17:44 ` Clem Cole
2020-07-20 17:52 ` Clem Cole
2020-07-20 17:56 ` Warner Losh
2020-07-20 18:08 ` Richard Salz
2020-07-20 18:07 ` Will Senn
2020-07-24 18:29 ` Random832
2020-07-24 18:46 ` Will Senn
2020-07-24 18:57 ` Clem Cole
2020-07-24 19:21 ` Will Senn [this message]
2020-07-25 2:00 ` Dave Horsfall
2020-07-20 17:55 ` Warner Losh
2020-07-20 18:11 ` Will Senn
2020-07-20 18:41 ` Clem Cole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28e558bd-d047-9a13-09d2-638df537a915@gmail.com \
--to=will.senn@gmail.com \
--cc=clemc@ccc.com \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).