From nobody Mon Sep 16 14:53:03 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4X6nwD6wlFz5WC9t for ; Mon, 16 Sep 2024 14:53:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4X6nwD5HMnz48mK for ; Mon, 16 Sep 2024 14:53:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x530.google.com with SMTP id 41be03b00d2f7-7db54269325so1142934a12.2 for ; Mon, 16 Sep 2024 07:53:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1726498395; x=1727103195; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XP+ZQ7ZrnG91g/tjh95zbvMJHVe7nNKkiGIzguMTv6A=; b=EeHedjdfYqfb5oDLVq8A5KERKHTIROCGFqdsrI6zGGsO/MB+4KtMtIWZK4R4f+jo+t AvQYJnAmQsOSibmjswOZeoojolxhYG/rQDt9Yq3pxBVUXKR1e5MsphaSR/DiZq5L4L1+ MTq3Ei6SBAypNDRkcoGwrS9MNqEr8+iGtis71BmGw2Mhjazwqgjr5oNSmgqWejRFnyzA OWnsFtrMbMFd3b0WBP+cjqj+FjoG/fpjqHRswdABdDVcokmLHzrwDRqm7yueqX+lXqzL 4Ftx61Ph48L4eLC7h+w7q3Vlg8gMOmG9xVhDFdwgT0JB1CE2Pb0nEQ41eV4BH+9euKrb 35og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726498395; x=1727103195; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=XP+ZQ7ZrnG91g/tjh95zbvMJHVe7nNKkiGIzguMTv6A=; b=tlW4xeNYVy1deC7ht0w3ipBRXlLgi5xpBQq7IF+2zggw3zN5B7+wAJ75oz3Cu20xSN wKkFZQP4zw9TOjfEetzqeP9DsO7TxTtOLapKFgsCRe8GqmejEbmh3rcgHlgdqi+nigNn d2yPWy3cNwMAvY8Y7p0MD9gI4j/eLry1/XnZ8SpfZEFAaYAcl0gaGVep3J6yeaCdJ2TM oTTS3HDPS25tYXQYWRE+250Cp1TQqGkT599VesBKLla1/9cncAg8bOt6Hpq6MQ5Htn/o nebRaSd7T5bA5s+ElZEMEt85BcnhQQzhEWhQcy5jW4t0CIyjkTxzv10JYM8qEBytY8MB Xu8w== X-Gm-Message-State: AOJu0Yx4z6zNULnH7Wi/bOaxWbM528yA42R4CWul2aiHl1czQ3Zue1tZ 90PQojJStf4WGWVlzIbzlua69q7omi1h8vU2BidAasNE5buHICaR3UWLWZTYmh6TX8xfZbaAYZf flc4gm7I15oVf7esG+Lk2atTNpXo8+PTnsvBszgumTyxs3mmXtLc= X-Google-Smtp-Source: AGHT+IGi0buY32BHZtlJNPRVdzKRmkJu3LUmEH0MvR5/r7TayQvCcicjK8yUdkCXjuaPFjueMW9ZX1BOSRYlxoBT+pk= X-Received: by 2002:a05:6a20:d80f:b0:1c1:92f8:d3c6 with SMTP id adf61e73a8af0-1d112db24a8mr17396710637.27.1726498395198; Mon, 16 Sep 2024 07:53:15 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <1e614684-1cba-ef01-34dc-d9300db2d927@macktronics.com> <20240916141330.995C554A@slippy.cwsent.com> In-Reply-To: <20240916141330.995C554A@slippy.cwsent.com> From: Warner Losh Date: Mon, 16 Sep 2024 15:53:03 +0100 Message-ID: Subject: Re: change in /usr/bin/bc with CTRL-d no longer exit To: Cy Schubert Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000008d472706223dbb34" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4X6nwD5HMnz48mK --0000000000008d472706223dbb34 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Sep 16, 2024, 3:13=E2=80=AFPM Cy Schubert wrote: > In message , void writes: > > On Sun, Sep 15, 2024 at 03:16:46PM -0500, Dan Mack wrote: > > >On 14.1 and prior, a CTRL-d will exit a bc session. > > > > > >Today I noticed that on 3 different 15-CURRENT systems, it appears to > > >be ignored. Works fine otherwise and I can exit the bc session with > > >the 'quit' command okay. > > > > > >I re-tested this on the system console on fresh login just to rule out > > >any terminal madness. > > > > > >Here's a paste of what I see: > > > > > >https://tpaste.us/VYya > > > > > >I did a fresh install of 14.1 and it works as it did previously. > > > > > >No biggie, just wondering if anyone else on -CURRENT can confirm/deny > > >this change on their system. > > > > [void@vm5 ~ ] uname -KU > > 1400504 1400504 > > [void@vm5 ~ ] echo 2+2 | bc -l > > 4 > > > > [void@vm3 ~ ] uname -KU > > 1500023 1500023 > > [void@vm3 ~ ] echo 2+2 | bc -l > > 4 > > Of course the above works because the regression only affects tty users. > bc(1) now ignores EOF on the terminal while the above still works. You ca= n > circumvent this by putting "export BC_TTY_MODE=3D0" into your .profile. T= he > side effect is that line editing will no longer work. > The irony here is that i fixed thus very bug 2 or 3 years ago. Warner > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: https://FreeBSD.org > NTP: Web: https://nwtime.org > > e^(i*pi)+1=3D0 > > > > --0000000000008d472706223dbb34 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Sep 16, 2024, 3:13=E2=80=AFPM Cy Schubert <= Cy.Schubert@cschubert.com&= gt; wrote:
In message <ZudpAKZS7= JgS9ZZ_@int21h>, void writes:
> On Sun, Sep 15, 2024 at 03:16:46PM -0500, Dan Mack wrote:
> >On 14.1 and prior, a CTRL-d will exit a bc session.
> >
> >Today I noticed that on 3 different 15-CURRENT systems, it appears= to
> >be ignored.=C2=A0 Works fine otherwise and I can exit the bc sessi= on with
> >the 'quit' command okay.
> >
> >I re-tested this on the system console on fresh login just to rule= out
> >any terminal madness.
> >
> >Here's a paste of what I see:
> >
> >https://tpaste.us/VYya
> >
> >I did a fresh install of 14.1 and it works as it did previously. > >
> >No biggie, just wondering if anyone else on -CURRENT can confirm/d= eny
> >this change on their system.
>
> [void@vm5 ~ ] uname -KU
> 1400504 1400504
> [void@vm5 ~ ] echo 2+2 | bc -l
> 4
>
> [void@vm3 ~ ] uname -KU
> 1500023 1500023
> [void@vm3 ~ ] echo 2+2 | bc -l
> 4

Of course the above works because the regression only affects tty users. bc(1) now ignores EOF on the terminal while the above still works. You can =
circumvent this by putting "export BC_TTY_MODE=3D0" into your .pr= ofile. The
side effect is that line editing will no longer work.

The irony here is that= i fixed thus very bug 2 or 3 years ago.

<= div dir=3D"auto">Warner=C2=A0
--
Cheers,
Cy Schubert <Cy.Schubert@cschubert.com>
FreeBSD UNIX:=C2=A0 <cy@FreeBSD.org>=C2=A0 =C2=A0Web:=C2=A0 ht= tps://FreeBSD.org
NTP:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<cy@nwtime.org>=C2=A0 =C2= =A0 Web:=C2=A0 https://nwtime.org

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 e^(i*pi)+1=3D0



--0000000000008d472706223dbb34--