Agreed there is no likelihood of a patch to 3.2. However, this version of bash still has a significant presence in the wild and this bug is breaking an installation script, so I am looking for a POSIX-compliant (and works under Cygwin) alternative that avoids this bug so the script can be modified.
As a step towards getting there, and out of plain curiosity, I would also like to know if this is due to a known bug and if so, what the underlying cause is and in what versions it has been fixed. On Wed, Jan 9, 2019 at 11:09 PM Eduardo Bustamante <dual...@gmail.com> wrote: > On Wed, Jan 9, 2019 at 10:54 PM Jeremy <asfbugzi...@nuru.net> wrote: > (...) > > 3.2.57(1)-release (x86_64-apple-darwin15) > > > > > > This is on MacOS 10.11.6. If there is a better place for me to report > this > > bug, please let me know. > > Have you tried the latest version? Bash 5.0 was just released: > https://lists.gnu.org/archive/html/bug-bash/2019-01/msg00063.html > > I don't think you'll be seeing any updates in the OS X provided > version of bash, so there's no point in even trying to back-port any > fixes to 3.2 > >