From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] # (was Re: sh: cmd | >file)
Date: Tue, 07 Jan 2020 18:44:47 -0800 [thread overview]
Message-ID: <m1ip1Ky-0036tPC@more.local> (raw)
In-Reply-To: <CANCZdfqsBFwxwjb5kEnE6FTGgAA4ZH_L_AqyB4A1eoUeEoL1Gg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
At Mon, 6 Jan 2020 17:39:39 -0700, Warner Losh <imp@bsdimp.com> wrote:
Subject: Re: [TUHS] # (was Re: sh: cmd | >file)
>
>
> Or you might have cut and paste the commands from a script to test
> something, or to redo something by hand that failed for some reason.
Cut & Paste?
Most of us couldn't do that until the very late 1980's at earliest!
The poor man's cut&paste was to do something like 'sed -n 3,9p script |
sh', but I don't think I ever did that with csh in the days when a '#'
comment was for scripts only, so I don't know if old csh treated a pipe
on stdin as a script or not.
--
Greg A. Woods <gwoods@acm.org>
Kelowna, BC +1 250 762-7675 RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com> Avoncote Farms <woods@avoncote.ca>
[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-01-08 2:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 6:30 Brian Walden
2020-01-06 22:50 ` Dave Horsfall
2020-01-07 0:39 ` Warner Losh
2020-01-08 2:44 ` Greg A. Woods [this message]
2020-01-07 15:24 ` Clem Cole
2020-01-07 22:13 ` Dave Horsfall
2020-01-07 22:26 ` Bakul Shah
2020-01-07 22:56 ` Dave Horsfall
2020-01-08 5:20 Brian Walden
2020-01-08 6:25 ` Bakul Shah
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=m1ip1Ky-0036tPC@more.local \
--to=woods@robohack.ca \
--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).