From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Traditional method of dealing with embedded shar files
Date: Sat, 25 Jul 2020 12:00:23 +1000 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2007251157170.76447@aneurin.horsfall.org> (raw)
In-Reply-To: <a2c38198-3735-4511-8f36-3e75abcf46d4@www.fastmail.com>
On Fri, 24 Jul 2020, Random832 wrote:
> For whatever it's worth, you can do the exact same thing as vi with sed
> in this case: 1,/====/d
It's been a while since I had to use it, but didn't "unshar" do this sort
of thing, and in a safe manner too? You'd be out of your mind to blindly
run the shell on some anonymous shar file...
-- Dave
next prev parent reply other threads:[~2020-07-25 2:01 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
2020-07-25 2:00 ` Dave Horsfall [this message]
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=alpine.BSF.2.21.9999.2007251157170.76447@aneurin.horsfall.org \
--to=dave@horsfall.org \
--cc=tuhs@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).