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

[Roman Rakus]

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:
> $ ls $HOME/bin<TAB><RETURN>
> "ls: cannot access $HOME/bin: No such file or directory"
quoting and completion
> 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.
Why would bash do that?
> 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.
And to be complete, there is a bug also in bash-completion package, 
which need to be fixed.
Many people uses bash-completion, even they don't know it.

RR