On Mon, Feb 03, 2025 at 23:37:12 -0500, Zeffie via Bug reports for the GNU Bourne Again SHell wrote: > 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>
That was part of the reporter's demonstration that bash DOES NOT have the same problem as the FreeBSD /bin/sh. Granted, the wording used in the bug report is not very clear. It's difficult to conclude much from the reporter's bash sessions. But my reading led me to understand that he was contrasting the behavior of bash against that of FreeBSD's /bin/sh, and then arguing that FreeBSD's /bin/sh should behave as bash does. Now that everyone has read the FreeBSD bug report multiple times, can you tell us how to reproduce the problem in bash? Also note that there is a readline setting which controls this behavior in bash. It's configured via the echo-control-characters readline variable, which is "on" by default, at least in bash 5.2. The behavior in older versions may differ.
