bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Red-Hat Bug 825751 - bash-completion fails on environment variables


From: Linda Walsh
Subject: Re: Red-Hat Bug 825751 - bash-completion fails on environment variables
Date: Thu, 07 Jun 2012 14:22:52 -0700
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.24) Gecko/20100228 Lightning/0.9 Thunderbird/2.0.0.24 Mnenhy/0.7.6.666



Clark WANG wrote:
On Mon, May 28, 2012 at 11:32 PM, John E. Malmberg <address@hidden> 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/2011-12/msg00035.html
-----
In reading the messages quoted above, I'm not sure some people
understand the severity of the bug.

This isn't a matter of preference... its a real bug.

Ex:
$ ls $HOME/bin<TAB><RETURN>
"ls: cannot access $HOME/bin: No such file or directory"

It's not about expansion or non-expansion during the editing phase--
that would be a matter of preference, it's that when you hit enter,
it doesn't expand the variables -- which I can't see being useful for
anyone.

Note -- this is the same type of problem as Bash not correcting
the case of path components.

Bash isn't correcting the lines anymore so that final
expansions match real paths...


When I originally heard this discussion, I thought -- it's a matter
of preference, though I think I prefer expansion, I could see times
when it might be a hassle (if the var was a REAL long expansion,
it might overflow the line)...but having it not work at all...

That's not useful for anyone.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]