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 32725 invoked from network); 6 Jul 2020 20:49:59 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 6 Jul 2020 20:49:59 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 1ADDE9C6B2; Tue, 7 Jul 2020 06:49:55 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 5828794598; Tue, 7 Jul 2020 06:48:55 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="DgbkdE+S"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 6DE1C94598; Tue, 7 Jul 2020 06:48:52 +1000 (AEST) Received: from mail-qt1-f169.google.com (mail-qt1-f169.google.com [209.85.160.169]) by minnie.tuhs.org (Postfix) with ESMTPS id 9A7EA94588 for ; Tue, 7 Jul 2020 06:48:51 +1000 (AEST) Received: by mail-qt1-f169.google.com with SMTP id v19so30095126qtq.10 for ; Mon, 06 Jul 2020 13:48:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wTNffX4uF/wQ0WOzuNoIteD520+1bLymQMwJuz+A8uA=; b=DgbkdE+SgQIol+ZKFvhwQzg26gOGyqniyyiTqf1djcSMSrxaENy4OrVuzswHFcI5mx Zxre1PZiD7+m6YT41D0ETUm9WaapNzBZ+r4is7Up6zG+gVFO6737KhEgf//h5HYw2cOH WMGY/sojeQTdvN/St2gkVkVTnfuN5s+eA61cc= 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=wTNffX4uF/wQ0WOzuNoIteD520+1bLymQMwJuz+A8uA=; b=GMX8pcUyN+3C/Xq4jnCdMJlupbj/IyhcX6IulRoMR5cjbCXhN6c745VmvU/HDOR+sk hZznQUx8XqftA/GxxHG7QeiXQINsdRvLIzesJoWgd7qInQ5g4QNV/okdcSqwsurWGOaz ii+sMy1UgmIvJ3LqEE+LjdqjmUpSZYxBZFKSaB9T6F8d1V/6ZEfeSsmcmeM63qF03wIY XJghdKzCBJ/v4R3LiuT6j9bHmQNz5yQB6dUobBzsAjYgNWSB52G/J++x+K6KkMAGuOea iplll1i0eto9pOcf7uCgHLDZQIHEch2ykziCh0fqWSr6mjNWLeyMau3hMaRDQdcf9ElX HdzQ== X-Gm-Message-State: AOAM5308m95n8Mwy/rA0QSENC/U66JYVW7LJkIqlOZPaOukxwQWeUnSe +Tc1XWRIKNouIiZSo6R5a4Xax3+vet6Niu8mJ2hNkQ== X-Google-Smtp-Source: ABdhPJypuFxySi6FjtlLJAlHXKlvTz/R0WcIZscRQZ8FNGzOEp6oe6WM/H1u45jqgEPcInn2GxKCVzaK/KpNYnLA3R0= X-Received: by 2002:ac8:130d:: with SMTP id e13mr51587862qtj.253.1594068530563; Mon, 06 Jul 2020 13:48:50 -0700 (PDT) MIME-Version: 1.0 References: <202007061919.066JJ51w031385@freefriends.org> In-Reply-To: From: Clem Cole Date: Mon, 6 Jul 2020 16:48:24 -0400 Message-ID: To: John Cowan Content-Type: multipart/alternative; boundary="00000000000083292c05a9cc00d8" 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" --00000000000083292c05a9cc00d8 Content-Type: text/plain; charset="UTF-8" below... On Mon, Jul 6, 2020 at 3:36 PM John Cowan wrote: > > 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 > need a closing / for ed, but ex/vi accepts the naked version. > > and that gives me > > foo^@bar > > I call that a bug. (This is vim 8.1). > In fairness, early vi did this too. nvi (Bostic's rewrite) which came out around 4.3 or 4.4 fixed it. > > 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. > I agree, I have tried to us the ^V^J idiom with different success. Since vim has been forced down my throat, I tend to not try it, and as you say, switch editors when I need to add a newline. > > 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. > Amen ... vim's undo can be ... a ... challenging for original vi user - but that has been debated here a few times and I'd rather not see another war. Clem --00000000000083292c05a9cc00d8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
below...

On Mon, Jul 6, 2020 at 3= :36 PM John Cowan <cowan@ccil.org&= gt; wrote:

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
need a closing / for ed, but ex/vi accepts the naked version.

=C2=A0

and that gives me

foo^@bar

=
I call that a bug.=C2=A0 (This is vim 8.1).
In fairness, early vi did this too.=C2=A0 nvi (Bostic'= ;s rewrite) which came out around 4.3 or 4.4 fixed it.

= =C2=A0

It certainly wouldn'= t occur to me to use ^V^M, anyhow:=C2=A0 ^V^J would seem more reasonable, b= ut ^V is ignored in that context.
I agree, I have tried to us the ^V^J idiom=C2=A0with different success.=C2=A0 Since vim has been forced down my throat, I tend to not try= it, and as you say, switch editors when I need to add a newline.

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.=C2= =A0 If you had never been in vi-mode (as I usually had not) it undid everyt= hing 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 i= n case.
Amen ...=C2=A0 =C2=A0vim'= ;s undo=C2=A0can be ...=C2=A0 a ... challenging for original vi user - but = that has been debated here a few times and I'd rather not see another w= ar.=C2=A0
Clem

--00000000000083292c05a9cc00d8--