On 5/29/2012 7:12 AM, Chet Ramey wrote:
On 5/28/12 11:32 AM, John E. Malmberg wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=825751
bash-4.2.24-1.fc16.i686
Please take a look at
http://git.savannah.gnu.org/cgit/bash.git/log/?h=direxpand
and see if that behaves the way you like.
Thanks,
In the discussion that you referenced earlier, it mentions that it was
considered making this behavior controlled by a settable parameter.
Is that implemented with this patch?
Is this eventually going to be part of an official patch?
This issue was reported to me by the same person that submitted the
Red-Hat Bug report, and not something that is directly impacting me.
I did search for the issue before posting, but apparently did not use
the right keywords, and I did not see the issue addressed in any of the
official patches.
In my current spare time project below, I am planning to try to just
implement as much as the current Bash + official patch behavior as I
can, and probably not implement the optional patches. Once I get the
base 4.2 release functional, then I will apply all the official patches
to the source.
LION> bash --version
GNU bash, version 4.2.0(1)-release (ia64-dec-vms)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
GNV-2.1-3-JEM-2 May 12 2012 19:36:33
On this platform, file names with $ in them tend to show up as they have
special meaning.
BASH-4.2$ echo *\$*
GNV$BASH.DSF GNV$BASH.EXE GNV$BASH.MAP GNV$SHELL.C_FIRST
GNV$VERSION.C_FIRST gnv$bash_startup.com gnv$main_wrapper
gnv$vms_main_link.exe
Regards,
-John
