In message <CANCZdfpe86cZeabqAvpo-q1OtYxLggo7s9rZkreFKX=PqA=Ojw@mail.gmail.c om> , Warner Losh writes: > --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 <cy.schub...@cschubert.co= > m> wrote: > > > 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 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 >
It's curious (or maybe not) how some bugs keep returning with a time and time again. -- Cheers, Cy Schubert <cy.schub...@cschubert.com> FreeBSD UNIX: <c...@freebsd.org> Web: https://FreeBSD.org NTP: <c...@nwtime.org> Web: https://nwtime.org e^(i*pi)+1=0
