From: Ken Thompson <kenbob@gmail.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: ed: multiple addresses (with semicolons)
Date: Fri, 8 Jul 2022 09:01:43 -0700 [thread overview]
Message-ID: <CAMP=X_k+S1pU_k7KiGztfKaMe3bAZGTx94=eEGMScdKFkhYzPA@mail.gmail.com> (raw)
In-Reply-To: <CAKH6PiUr9FQ7N06_iSxQ=4vbQG137aaiNFSUmQ3JB3qjjXjFuw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
On Fri, Jul 8, 2022 at 6:24 AM Douglas McIlroy <
douglas.mcilroy@dartmouth.edu> wrote:
> The interpretation of a string of addresses separated by commas and/or
> semicolons was already defined in the v1 man page for ed.
>
> Ed was essentially a stripped-down version of Multics qed. The latter
> was originally
> written by Ken. Unfortunately the "Multics Condensed Guide" online at
> multicians.org describes how strings of addresses were interpreted
> only by canonical examples for the various editing requests.
>
> I have no specific memory of semicolons in qed. I have a vague
> recollection that semicolons originated in ed, however you should put
> no trust in this. Maybe Ken remembers.
>
> Doug
>
String of addresses was same for qed and ed.
[-- Attachment #2: Type: text/html, Size: 1177 bytes --]
next prev parent reply other threads:[~2022-07-08 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 13:23 [TUHS] " Douglas McIlroy
2022-07-08 16:01 ` Ken Thompson [this message]
2022-07-08 19:13 ` [TUHS] " 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
-- strict thread matches above, loose matches on Subject: below --
2022-07-11 17:30 Douglas McIlroy
2022-07-18 10:52 ` markus schnalke
2022-07-08 21:36 Douglas McIlroy
2022-07-11 14:40 ` markus schnalke
2022-07-08 7:47 [TUHS] " markus schnalke
2022-07-08 8:09 ` [TUHS] " markus schnalke
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='CAMP=X_k+S1pU_k7KiGztfKaMe3bAZGTx94=eEGMScdKFkhYzPA@mail.gmail.com' \
--to=kenbob@gmail.com \
--cc=douglas.mcilroy@dartmouth.edu \
--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).