From: markus schnalke <email@example.com>
Subject: [TUHS] Re: ed: multiple addresses (with semicolons)
Date: Fri, 08 Jul 2022 21:13:17 +0200 [thread overview]
Message-ID: <1o9tPh-48Wfirstname.lastname@example.org> (raw)
thanks for your replies, Doug and Ken.
Unfortunately I wasn't able to find the ``Multics Condensed Guide''
on multicians.org. Can someone please provide a link?
Interrestingly, I discovered that qed had double quotes (") as a
comment command, which simply ignores the rest of the line. As far
as I know, there's no way to comment ed scripts. Why was that
In ex(1) the " comment command reappeared. I've always wondered
why it used this character for comments. Seems it comes from qed,
leaping over ed, but reappearing in ex.
[2022-07-08 09:01] Ken Thompson <email@example.com>
> On Fri, Jul 8, 2022 at 6:24 AM Douglas McIlroy <firstname.lastname@example.org>
> 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.
> String of addresses was same for qed and ed.
next prev parent reply other threads:[~2022-07-08 19:14 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 ` [TUHS] " Ken Thompson
2022-07-08 19:13 ` markus schnalke [this message]
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
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).