From: John Cowan <cowan@ccil.org>
To: arnold@skeeve.com
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] v7 uucp debugging help requested
Date: Mon, 6 Jul 2020 15:36:02 -0400 [thread overview]
Message-ID: <CAD2gp_Rrg+=KUeCtayVBssGiY46WjQk5c-pYrdODyJWcjo9VOQ@mail.gmail.com> (raw)
In-Reply-To: <202007061919.066JJ51w031385@freefriends.org>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
On Mon, Jul 6, 2020 at 3:19 PM <arnold@skeeve.com> wrote:
Huh? I've never seen this, in over 20 years of using vim. To
> insert a newline just use
>
> s/foobar/foo^V^Mbar/
>
> where ^V^M are Control-V Control-M.
>
I never thought of that; I've always tried what works in ed, namely:
s/foobar/foo\
bar
and that gives me
foo^@bar
I call that a bug. (This is vim 8.1).
It certainly wouldn't occur to me to use ^V^M, anyhow: ^V^J would seem
more reasonable, but ^V is ignored in that context.
Before vim 7 there was a bug so bad I had to use nvi (and, often enough,
compile it from source): at that time, undo undid everything back to the
last action in vi-mode. If you had never been in vi-mode (as I usually had
not) it undid everything back to the last file-loading command! That one
made me grind my teeth a lot. Even now I habitually write before undoing,
just in case.
John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org
A male Jang appeared at my side. "Get a grip on yourself," he said.
"Get a grip on your graks," I suggested. --Tanith Lee, Drinking Sapphire
Wine
[-- Attachment #2: Type: text/html, Size: 1896 bytes --]
next prev parent reply other threads:[~2020-07-06 19:37 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 [this message]
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_Rrg+=KUeCtayVBssGiY46WjQk5c-pYrdODyJWcjo9VOQ@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=arnold@skeeve.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).