From: "Ron Natalie" <ron@ronnatalie.com>
To: "TUHS main list" <tuhs@tuhs.org>
Subject: [TUHS] Re: vi in cooked mode?
Date: Fri, 04 Nov 2022 18:33:34 +0000 [thread overview]
Message-ID: <embfcc1a1d-6a12-4624-a085-f72b735d257b@820bff6f.com> (raw)
In-Reply-To: <CAC20D2OFhwHzb0CzQRN=+wzqjy_ygULGE56rcsqKbHGE_cZB0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
>
>v6 vs v7 PDP-11 vs Vax much less vi vs emacs.
>
Amusingly, as weith many of us, I got my start with "ed." I never
actually learned vi. By the time I was ready to move up to screen
editors, the emacs-ish things were available to me.
I did a small stint using INed (Rand-editor variant) at one job.
My employees always found it amusing that if I was stuck on a machine
that didn't have some emacs-ish thing, I just used ed. They marvelled
at my ability to complex substitutions with the s/// regular
expressions.
[-- Attachment #2: Type: text/html, Size: 2228 bytes --]
next prev parent reply other threads:[~2022-11-04 18:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 19:43 [TUHS] " Diomidis Spinellis
2022-11-03 20:26 ` [TUHS] " Clem Cole
2022-11-03 20:27 ` Clem Cole
2022-11-03 20:55 ` Warner Losh
2022-11-03 21:34 ` Clem Cole
2022-11-03 22:28 ` Warner Losh
2022-11-03 22:52 ` Ron Natalie
2022-11-04 6:43 ` Lars Brinkhoff
2022-11-04 15:18 ` Dan Cross
2022-11-04 17:54 ` Lars Brinkhoff
2022-11-04 18:33 ` Ron Natalie [this message]
2022-11-04 23:42 ` Theodore Ts'o
2022-11-05 0:45 ` Dave Horsfall
2022-11-05 1:02 ` Larry McVoy
2022-11-05 1:25 ` Bakul Shah
2022-11-05 1:40 ` Larry McVoy
2022-11-05 2:31 ` Rich Salz
2022-11-05 3:44 ` Bakul Shah
2022-11-05 18:34 ` Theodore Ts'o
2022-11-05 9:29 ` Otto Moerbeek via TUHS
2022-11-04 22:13 ` Mary Ann Horton
2022-11-03 20:17 Noel Chiappa
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=embfcc1a1d-6a12-4624-a085-f72b735d257b@820bff6f.com \
--to=ron@ronnatalie.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).