From: Will Senn <will.senn@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Traditional method of dealing with embedded shar files
Date: Fri, 24 Jul 2020 13:46:00 -0500 [thread overview]
Message-ID: <83465487-ed5e-8d1c-91e3-a201ccda6464@gmail.com> (raw)
In-Reply-To: <a2c38198-3735-4511-8f36-3e75abcf46d4@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On 7/24/20 1:29 PM, Random832 wrote:
> On Mon, Jul 20, 2020, at 14:07, Will Senn wrote:
>> On 7/20/20 12:52 PM, Clem Cole wrote:
>>>
>>> On Mon, Jul 20, 2020 at 1:25 PM Will Senn <will.senn@gmail.com> wrote:
>>>> My questions for y'all are how would you go about doing this? Use vi to delete everything through the ==== cut here line?
>>> Yep
>> Nice, seemed easy enough to me, but I was expecting real Unix folks use
>> sed | awk | indent type answers.
> For whatever it's worth, you can do the exact same thing as vi with sed in this case: 1,/====/d
>
> I wasn't there, so I can't say if this was done in practice or if there was even enough uniformity in the markers for it to be reliable in theory [perhaps /^#!/,$p ?]
I'm just getting comfortable using sed, thanks for the simplification.
Will
--
GPG Fingerprint: 68F4 B3BD 1730 555A 4462 7D45 3EAA 5B6D A982 BAAF
[-- Attachment #2: Type: text/html, Size: 1871 bytes --]
next prev parent reply other threads:[~2020-07-24 18:46 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 [this message]
2020-07-24 18:57 ` Clem Cole
2020-07-24 19:21 ` Will Senn
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=83465487-ed5e-8d1c-91e3-a201ccda6464@gmail.com \
--to=will.senn@gmail.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).