From: Larry McVoy <lm@mcvoy.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: vi in cooked mode?
Date: Fri, 4 Nov 2022 18:02:47 -0700 [thread overview]
Message-ID: <20221105010247.GG29525@mcvoy.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2211051137590.43868@aneurin.horsfall.org>
On Sat, Nov 05, 2022 at 11:45:26AM +1100, Dave Horsfall wrote:
> A boss of mine insisted that everyone had to learned "ed", because after a
> system crash it might be the only editor available; that, or having to
> dial in over a slow modem.
Same. Though vi in ex mode was also good.
I also got a little corrupted by whatever editor came with BDS C, my
.exrc looks like this:
map # :.,$
map @ :1,.
Those came from that editor, # says do whatever to the end of the file,
@ says do whatever from the top of the file to here.
map , !}fmt
This came from Udi Manber, , runs your paragraph through fmt
map! \x01 \x14
I set shiftwidth to 4 spaces because when you have code like
if ((this big thing == that big thing) && (this other big thing) &&
(yet another big thing)) {
I use 4 spaces for what I call the continuation line. I used ^A to write
that example, why I don't like ^T is lost to me.
And yeah, I paren stuff that doesn't need to have parens, it just makes
the code more obvious.
set redraw ai aw terse
redraw I think is left over from modems, autoident because duh,
autowrite because who doesn't hack, hack, hack, ^Z, !cc? terse
because I'm not a newbie.
set sections=uhshSHNH
set paragraphs=PSPETSTEFSFEKSKECSCERSREDSDEIPNPLPPPTLABAIAELIB1B2HH
Troff.
set ts=8 sw=4
set shell=/bin/sh
set showmode
set textwidth=1000
set vb
Etc.
I've been carrying around that .exrc for around 40 years. Sheesh, I'm old.
next prev parent reply other threads:[~2022-11-05 1:03 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
2022-11-04 23:42 ` Theodore Ts'o
2022-11-05 0:45 ` Dave Horsfall
2022-11-05 1:02 ` Larry McVoy [this message]
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=20221105010247.GG29525@mcvoy.com \
--to=lm@mcvoy.com \
--cc=dave@horsfall.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).