On 06/07/2012 11:22 PM, Linda Walsh wrote:
In reading the messages quoted above, I'm not sure some people
understand the severity of the bug.
I do not.
And many people don't understand expansions, quoting, completions and
many other...
This isn't a matter of preference... its a real bug.
Ex:
Eric Blake wrote:
On 06/07/2012 03:22 PM, Linda Walsh wrote:
This isn't a matter of preference... its a real bug.
Ex:
$ ls $HOME/bin
"ls: cannot access $HOME/bin: No such file or directory"
Yes, we know. Ergo patch 29:
According to the the referred to discussion on this
issu
On 06/07/2012 03:22 PM, Linda Walsh wrote:
> This isn't a matter of preference... its a real bug.
>
> Ex:
> $ ls $HOME/bin
> "ls: cannot access $HOME/bin: No such file or directory"
Yes, we know. Ergo patch 29:
https://lists.gnu.org/archive/html/bug-bash/2012-05/msg00148.html
--
Eric Blake
Clark WANG wrote:
On Mon, May 28, 2012 at 11:32 PM, John E. Malmberg wrote:
Actual results:
ls \$HOME/
Already discussed for quite a few times. :) For example:
http://lists.gnu.org/archive/html/bug-bash/2011-12/msg00079.html
(patched attached)
http://lists.gnu.org/archive/html/bug-bash/201
On Tue, May 29, 2012 at 8:34 AM, John E. Malmberg wrote:
>
> 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 gn
On 5/29/12 8:34 AM, John E. Malmberg wrote:
> 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?
Yes a
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,
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.
Chet
--
``The lyf so short, the craft so long
On Mon, May 28, 2012 at 11:32 PM, John E. Malmberg wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=825751
>
> bash-4.2.24-1.fc16.i686
>
> Steps to Reproduce:
> 1. Activate a terminal running a bash shell
> 2. ls $HOME/
> 3.
>
> Actual results:
> ls \$HOME/
Already discussed for quite a few t
https://bugzilla.redhat.com/show_bug.cgi?id=825751
bash-4.2.24-1.fc16.i686
Steps to Reproduce:
1. Activate a terminal running a bash shell
2. ls $HOME/
3.
Actual results:
ls \$HOME/
I get the directory get expanded result on Bash 1.4.8 (VMS special
build) and on Bash 3.2.25(1)-release.
Rega
10 matches
Mail list logo