From: John Cowan <cowan@ccil.org>
To: Adam Thornton <athornton@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] v7 uucp debugging help requested
Date: Sat, 4 Jul 2020 14:34:07 -0400 [thread overview]
Message-ID: <CAD2gp_RdRyhWt=LoWjHc__waQJH0P_Q_cCmqso16ojr4PbydnA@mail.gmail.com> (raw)
In-Reply-To: <CAP2nic0vJMLNfR+spn0WsT3_T632F4Uw08N1_7wv8BF1_sXG4w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
On Sat, Jul 4, 2020 at 12:33 PM Adam Thornton <athornton@gmail.com> wrote:
The "s" editor is written by Webb Miller and appears in his book "A
> Software Tools Sampler."
>
Wow, I never knew about this book, though I know ST and STP well, and used
ST on RSX-11/M+ and VAX/VMS for $EMPLOYER in the 1980s. Is the rest of the
source code for the book available online anywhere?
Jez Higgins is rewriting the STP tools into modern C++. His blog posts are
at <https://www.jezuk.co.uk/tags/software-tools-in-c++.html> and the code
is at <https://github.com/jezhiggins/stiX>. He's rewritten the tools in
chapters 1 and 2 and part of 3.
Since I find ed thoroughly unpleasant to use, having a screen editor was a
> must for me to use v7 for any length of time, and s fills that role rather
> nicely.
>
Gotcha. I actually like line editors (you can't mung your file so
thoroughly with a single stray keystroke), but I'm willing to trade a
little standardosity for additional convenience, so I do almost all my
editing of prose and programs in `ex`, occasionally dropping into vi-mode
for matching open and close markers in Lisp and XML.
John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org
If you have ever wondered if you are in hell, it has been said, then
you are on a well-traveled road of spiritual inquiry. If you are
absolutely sure you are in hell, however, then you must be on the Cross
Bronx Expressway. --Alan Feuer, New York Times, 2002-09-20
[-- Attachment #2: Type: text/html, Size: 2449 bytes --]
next prev parent reply other threads:[~2020-07-04 18:35 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 [this message]
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
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='CAD2gp_RdRyhWt=LoWjHc__waQJH0P_Q_cCmqso16ojr4PbydnA@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=athornton@gmail.com \
--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).