Date: Mon, 16 Sep 2024 07:13:30 -0700 From: Cy Schubert <Cy.Schubert@cschubert.com> To: freebsd-current@freebsd.org Subject: Re: change in /usr/bin/bc with CTRL-d no longer exit Message-ID: <20240916141330.995C554A@slippy.cwsent.com> In-Reply-To: <ZudpAKZS7JgS9ZZ_@int21h> References: <1e614684-1cba-ef01-34dc-d9300db2d927@macktronics.com> <ZudpAKZS7JgS9ZZ_@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <ZudpAKZS7JgS9ZZ_@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. 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 can circumvent this by putting "export BC_TTY_MODE=0" into your .profile. The side effect is that line editing will no longer work. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org NTP: <cy@nwtime.org> Web: https://nwtime.org e^(i*pi)+1=0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240916141330.995C554A>