On 2025-02-03 23:29, Lawrence Velázquez wrote:
On Mon, Feb 3, 2025, at 11:08 PM, Zeffie via Bug reports for the GNU
Bourne Again SHell wrote:
READ THE BUG REPORT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284513
Yes, let's.
The default FreeBSD bourne shell /bin/sh seems to ignore
the terminal config flag echoctl and does not give the user
any visual feedback to confirm that CTRL-C was issued. When
one types anything on the input line for the default FreeBSD
/bin/sh and then you enter CTRL-c it is silent.
[...]
The FreeBSD default bourne shell needs to respect the
terminal echoctl flag correctly and output a "^C" char
sequence correctly. There should be some reasonable feedback
to let the user know what happened.
Okay, FreeBSD's default /bin/sh ignores echoctl. Sounds annoying.
Unsaid in the bug report is the fact that FreeBSD's default /bin/sh
is an Almquist shell, not bash (and not a traditional Bourne shell,
as the reporter's language implies).
https://www.in-ulm.de/~mascheck/various/ash/#freebsd
https://cgit.freebsd.org/src/tree/bin/sh/main.c?h=release/14.2.0-p1#n7
Ergo, the bug report demonstrates an issue in FreeBSD's ash. It
does not demonstrate an issue with bash. This doesn't rule out an
issue with bash, but the bug report does not provide evidence that
there is an issue with bash.
So what are we doing here?
This will also be the last time I respond to you.
Sad!
Yes you are...
READ THIS
<quote>
To be more clear here the GNU BASH shell that I tested with is merely
a test case and the configuration was very harsh :
$ ./configure --prefix=/home/dclarke/local --enable-threads=posix \
--enable-xpg-echo-default --enable-minimal-config \
--enable-strict-posix-default
</quote>
should he of added make for you!?
Zeffie
