From: Warner Losh <imp@bsdimp.com>
To: Win Treese <treese@acm.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] v7 uucp debugging help requested
Date: Thu, 9 Jul 2020 23:19:12 -0600 [thread overview]
Message-ID: <CANCZdfqCWbYsk_m5Vy-8W=dcqHXZXu=8KtEdhZENWGZv+qMJ-g@mail.gmail.com> (raw)
In-Reply-To: <A74C1AE2-9A7A-418A-AC14-1249CD91ACDB@acm.org>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Thu, Jul 9, 2020, 11:13 PM Win Treese <treese@acm.org> wrote:
>
> > On Jul 6, 2020, at 4:48 PM, Clem Cole <clemc@ccc.com> wrote:
> >
> >>
> >> I never thought of that; I've always tried what works in ed, namely:
> >>
> >> s/foobar/foo\
> >> bar
> > need a closing / for ed, but ex/vi accepts the naked version.
>
> In the mid 1980s, when I was working at MIT’s Project Athena,
> one day Jerry Saltzer (MIT CS professor, known for work on CTSS
> and Multics, among other things, and Technical Director for Athena)
> called me into his office.
>
> He was trying to edit a file with ed on his IBM PC/RT workstation,
> which was running IBM’s variant of 4.2BSD on it, and he wanted
> to know why his search
>
> /foo
>
> wasn’t working.
>
> I typed /foo/, and everything was fine.
>
> He looked at it and muttered, “Oh, you have to end it with a slash?
> When I wrote this for CTSS, you didn’t need to do that.”
>
Kids today.... get off my damn regex... even turning couldn't complete
this lot. Bah
:)
Warner
>
>
>
[-- Attachment #2: Type: text/html, Size: 1873 bytes --]
next prev parent reply other threads:[~2020-07-10 5:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 20:52 Adam Thornton
2020-07-03 21:26 ` Clem Cole
2020-07-03 22:38 ` Grant Taylor via TUHS
2020-07-04 0:28 ` Clem Cole
2020-07-04 0:31 ` Clem Cole
2020-07-04 19:33 ` Adam Thornton
2020-07-04 20:02 ` Clem Cole
2020-07-04 21:58 ` Adam Thornton
2020-07-05 5:42 ` Adam Thornton
2020-07-03 22:50 ` John Cowan
2020-07-04 16:33 ` Adam Thornton
2020-07-04 18:34 ` John Cowan
2020-07-04 18:44 ` Jon Forrest
2020-07-04 19:34 ` Adam Thornton
2020-07-06 4:12 ` Dave Horsfall
2020-07-06 4:18 ` Warner Losh
2020-07-06 6:51 ` arnold
2020-07-06 7:11 ` Michael Usher via TUHS
2020-07-06 13:57 ` Clem Cole
2020-07-06 18:51 ` John Cowan
2020-07-06 19:19 ` arnold
2020-07-06 19:36 ` John Cowan
2020-07-06 19:58 ` John Cowan
2020-07-06 20:48 ` Clem Cole
2020-07-07 6:21 ` arnold
2020-07-10 5:05 ` Win Treese
2020-07-10 5:19 ` Warner Losh [this message]
2020-07-14 2:52 ` Dave Horsfall
2020-07-06 21:47 ` Dave Horsfall
2020-07-07 6:23 ` arnold
2020-07-07 21:45 ` Dave Horsfall
2020-07-06 21:18 ` Dave Horsfall
2020-07-06 21:47 ` John Cowan
2020-07-07 1:30 ` [TUHS] Editors (was: v7 uucp debugging help requested) Greg 'groggy' Lehey
2020-07-04 0:35 [TUHS] v7 uucp debugging help requested Norman Wilson
2020-07-07 19:20 Norman Wilson
2020-07-07 22:47 ` Rob Pike
2020-07-07 23:42 ` Adam Thornton
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='CANCZdfqCWbYsk_m5Vy-8W=dcqHXZXu=8KtEdhZENWGZv+qMJ-g@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=treese@acm.org \
--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).