From: markus schnalke <email@example.com>
To: TUHS main list <firstname.lastname@example.org>
Subject: [TUHS] Re: ed: multiple addresses (with semicolons)
Date: Mon, 18 Jul 2022 12:52:01 +0200 [thread overview]
Message-ID: <1oDOM5email@example.com> (raw)
[2022-07-11 19:30] Douglas McIlroy <firstname.lastname@example.org>
> > More was I curious about the documentation of address chains in books.
> It was even discussed in Lomutu and Lomuto, "A Unix Primer", a pleasant
> book whose level is accurately described in the title.
Thanks for the recommendation of this book. I now have a copy and
am looking forward to reading it. It must have been a great book
for users at the time (mainly covers editing and formatting) and
now it looks to be a great book for someone interested in
understanding how the experience of using Unix must have been to
normal users back then.
Although the semicolon address separator is explained in section
10.2.1 (page 143), I couldn't find address chains or supplying
more addresses than necessary to commands mentioned in the book.
Of course, as I haven't fully read it yet, I could have missed it,
although I checked the relevant pages.
Nonetheless, I'm happy with this new (old) book, which I luckily
received in nearly mint condition. :-)
next prev parent reply other threads:[~2022-07-18 10:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 17:30 Douglas McIlroy
2022-07-18 10:52 ` markus schnalke [this message]
2022-07-22 16:17 ` [TUHS] Re: ed: f command (facts vs. file) markus schnalke
2022-07-22 17:14 ` Phil Budne
2022-07-23 5:47 ` markus schnalke
-- strict thread matches above, loose matches on Subject: below --
2022-07-08 21:36 [TUHS] Re: ed: multiple addresses (with semicolons) Douglas McIlroy
2022-07-11 14:40 ` markus schnalke
2022-07-08 13:23 [TUHS] " Douglas McIlroy
2022-07-08 16:01 ` [TUHS] " Ken Thompson
2022-07-08 19:13 ` markus schnalke
2022-07-09 8:10 ` steve jenkin
2022-07-09 8:22 ` Rob Pike
2022-07-10 3:50 ` Jon Forrest
2022-07-10 9:25 ` Angelo Papenhoff
2022-07-10 9:59 ` Ralph Corderoy
2022-07-08 7:47 [TUHS] " markus schnalke
2022-07-08 8:09 ` [TUHS] " markus schnalke
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).