From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, NICE_REPLY_A,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31010 invoked from network); 24 Jul 2020 19:22:41 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 24 Jul 2020 19:22:41 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 9D3879C9E7; Sat, 25 Jul 2020 05:22:36 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 680189C9DB; Sat, 25 Jul 2020 05:21:40 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="tayNZlpj"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 9392F9C8DE; Sat, 25 Jul 2020 05:21:37 +1000 (AEST) Received: from mail-oi1-f179.google.com (mail-oi1-f179.google.com [209.85.167.179]) by minnie.tuhs.org (Postfix) with ESMTPS id 129A19C8B1 for ; Sat, 25 Jul 2020 05:21:37 +1000 (AEST) Received: by mail-oi1-f179.google.com with SMTP id t4so8900968oij.9 for ; Fri, 24 Jul 2020 12:21:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=tvTiJbpFiOKbFLnxK6XC/ylj6vrucUs4tJsdBMYBXhk=; b=tayNZlpjR3DCNxQfHLB3pIi7tQcmK/Qf77Mr8sihjNsdHQLvpdLldVN7TpAdP+7AIF sAnuMoLcCtM1P6JDCmLWCF2XLKvXvrvu8e7zdyOFgOYZgO2Qi6TKDJH+mTPu/qo5G+74 VVxMTf244h44wm3/T2FIzVdh/W1C1+3wY02//SSXLxQobnCZWGNYB/1BXHR7q/LDxF94 xiPqEYDnqEKN4PX7/rMnUIkNY7UYZoO/8SjYyE4GmXPwnWlDLXIh0Q6UqaRZxKgHhNEx u/89Tpjl8hDevJiLGh+k2cBALQZyjzyAzb39+GUthAWJ3TF4rWAihbvHO6CDFyDq6vS7 OF9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=tvTiJbpFiOKbFLnxK6XC/ylj6vrucUs4tJsdBMYBXhk=; b=n9LB+bUFvlGfPqCE90qvjP+7FLiTvY96nwCEKPN20FRS7cdT0lp3rV8psIjjS3dWBc WsgmiRavJApDUcdadJPXTyu2OhnjlAcupdmJutgpg4hhMoF798+cZoF0vkF6P1qDqWrp EMmudlkO8K56X1FDMzboVyCsp9OE0bU767BD7+O2x3veYqbTDTBlASVja+Jc8V4WYpFa r70vJ5tZ5RYeQWjV6ukw6NxyVjY0UUJ5sST7742DpiZTzg3X7LC44gmUTKPmWyk9cBxz QebTvzex93ftk134AQIxllqYXD/WEVM80kAV7oA5TR4KozoiwdRwS3/9CPqFNFq/kw1h //1A== X-Gm-Message-State: AOAM533XKJMjgdLYloQwL8N8pBZ/2VT2MDcT6ciBrPt9pSxhEYsLqkff 1rnidSjRb0pF0daIxISUM68DDKUuDcE= X-Google-Smtp-Source: ABdhPJzsEaCEOAFvL+20KaM68UlGM/YsBaQxVg7/+spQpUG46Gvj4S1/LV2VaPkT9Iv6491rqMZ7Ig== X-Received: by 2002:aca:4884:: with SMTP id v126mr9564095oia.98.1595618495825; Fri, 24 Jul 2020 12:21:35 -0700 (PDT) Received: from terra.local (99-139-148-170.lightspeed.rcsntx.sbcglobal.net. [99.139.148.170]) by smtp.gmail.com with ESMTPSA id b3sm1606050ooa.27.2020.07.24.12.21.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Jul 2020 12:21:35 -0700 (PDT) To: Clem Cole References: <78041442-c5e5-1b5c-8565-b6d31f23ec1b@gmail.com> <83465487-ed5e-8d1c-91e3-a201ccda6464@gmail.com> From: Will Senn Message-ID: <28e558bd-d047-9a13-09d2-638df537a915@gmail.com> Date: Fri, 24 Jul 2020 14:21:31 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------44E0037CEF510D66D98BB314" Content-Language: en-US Subject: Re: [TUHS] Traditional method of dealing with embedded shar files X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" This is a multi-part message in MIME format. --------------44E0037CEF510D66D98BB314 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 7/24/20 1:57 PM, Clem Cole wrote: > > > On Fri, Jul 24, 2020 at 2:47 PM Will Senn > 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 --------------44E0037CEF510D66D98BB314 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
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> 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
--------------44E0037CEF510D66D98BB314--