From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 24559 invoked from network); 6 Jul 2020 19:37:13 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 6 Jul 2020 19:37:13 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 192839C735; Tue, 7 Jul 2020 05:37:10 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 48BE29C6B2; Tue, 7 Jul 2020 05:36:18 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ccil-org.20150623.gappssmtp.com header.i=@ccil-org.20150623.gappssmtp.com header.b="htwUdduz"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id E8E0794598; Tue, 7 Jul 2020 05:36:14 +1000 (AEST) Received: from mail-qv1-f44.google.com (mail-qv1-f44.google.com [209.85.219.44]) by minnie.tuhs.org (Postfix) with ESMTPS id 688A294588 for ; Tue, 7 Jul 2020 05:36:14 +1000 (AEST) Received: by mail-qv1-f44.google.com with SMTP id t11so15704815qvk.1 for ; Mon, 06 Jul 2020 12:36:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Uu7F/YzNMKjKWggoN8VWWAv6k1KXKe6imET6T0Dnt/0=; b=htwUdduzDXGEOUgDpyysk+yFjBGc+TGcnv528xUBcxYhrpLyKZe4qcwLqgln5+OB9J OXIvV2XilDCW49FJMNt88QeCXtSePv152XLaXpoVtB1I4sWP0a/VUjPV6OgkDoBjS73v TqDhDv6rVHCDDOsmuRtFM4OprYu0UTdAOB8w0kv5Z02yRr6Zfp2SNuiw8SyA4w0ZAUyB odBkpISFqN8igQn0N6Yih0WkeM4OAQbWGZXpmrHAQa4F5uNrMTICIXbxC9Abt+TCiSia V4wBNgSKhMIWvbKjWPc1SLmkPcCJ6eYNhT/XhEK3UzDaVbTdzWdvKkF/E9HjfEbWBRsF DjSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Uu7F/YzNMKjKWggoN8VWWAv6k1KXKe6imET6T0Dnt/0=; b=CU0kPRKIY5cBuRbz2NL0MI7egTJfBYVd0fiE0Pc3aJmG/i0Y5fiVHUD8lVy6T1g+sS 8wVwgjGqh1JyJj6tuJepSTjczKkLa8LZNdJUzAu8q5EY7VTGJUQq0gPc8qtlorIYSsnN kUM5oO7m9W5rQCX8h39s3D5cc95EzsryTHqmQIgTJfiAJ++9w8lyp6jfxrjVtxQk0Nh7 ta1krmqPzerUvhXaRf3HcTAVVbIgmQ/tKOwrSWqEJv/Qkftirk5eLt5TWIC1G3dAsKpc 0d0yaHt004N58DSMu8ThkNKISfC2g7QzLtOowgMB70S3SvajrVKSEmZ58VFMSYyQm9dq 4L2g== X-Gm-Message-State: AOAM533k5ZSumfvyrTVevDcM0vcJDqbyPVDFTz3Dzzl8pDT5yll4nSRR 8Xp78We1LmDpRvAPQUeVS//HI19OFftx7TTSU4OBtu6WcqmX+w== X-Google-Smtp-Source: ABdhPJyoWk+fPpIaz2mu7GnLgqXPN6Zlg4UhcP4cb5DNsGWcZjeBYZqJT4k867Je/IQbedUI64crZZvSo/vj2wfo9i4= X-Received: by 2002:a05:6214:927:: with SMTP id dk7mr48410888qvb.26.1594064173557; Mon, 06 Jul 2020 12:36:13 -0700 (PDT) MIME-Version: 1.0 References: <202007061919.066JJ51w031385@freefriends.org> In-Reply-To: <202007061919.066JJ51w031385@freefriends.org> From: John Cowan Date: Mon, 6 Jul 2020 15:36:02 -0400 Message-ID: To: arnold@skeeve.com Content-Type: multipart/alternative; boundary="000000000000d07d2605a9cafc7e" Subject: Re: [TUHS] v7 uucp debugging help requested X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000d07d2605a9cafc7e Content-Type: text/plain; charset="UTF-8" On Mon, Jul 6, 2020 at 3:19 PM 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 --000000000000d07d2605a9cafc7e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

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

=C2=A0 =C2=A0 =C2=A0 =C2=A0 s/foobar/foo^V^Mbar/

where ^V^M are Control-V Control-M.

I n= ever thought of that; I've always tried what works in ed, namely:
=

s/foobar/foo\
bar

an= d that gives me

foo^@bar

= I call that a bug.=C2=A0 (This is vim 8.1).

It cer= tainly wouldn't occur to me to use ^V^M, anyhow:=C2=A0 ^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 enou= gh, compile it from source): at that time, undo undid everything back to th= e last action in vi-mode.=C2=A0 If you had never been in vi-mode (as I usua= lly had not) it undid everything back to the last file-loading command!=C2= =A0 That one made me grind my teeth a lot.=C2=A0 Even now I habitually=C2= =A0write before undoing, just in case.


<= div>
John Cowan =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http://vrici.lojban.org/~= cowan =C2=A0 =C2=A0 =C2=A0 =C2=A0cowan@ccil.org
A male Jang appeared at my side. =C2=A0= "Get a grip on yourself," he said.
"Get a grip on your gr= aks," I suggested. =C2=A0--Tanith Lee, Drinking Sapphire Wine

--000000000000d07d2605a9cafc7e--