Looks like a change in bash, i.e. I uninstalled bash-completion altogether and got the same behaviour:
$ cp $HOME/<TAB>

$ cp \$HOME/


reverting to bash-4.1 brings the old/expected behaviour back.

Source RPM: (none) => bash

Upstream change in behaviour, see http://lists.gnu.org/archive/html/bug-bash/2011-02/msg00274.html

CC: (none) => ahmadsamir3891

Sorry, forgot to add, we'll have to wait for upstream's decision on this.

upstream discussion vanished (dead link in comment 2 above), any news?

Looks like the archives of February and March have vanished somehow... unfortunately I am not subscribed to that ML (but if there's anything new, I guess the thread will be revived).

I checked it regularly and no news from upstream after the "I'll think about how to handle it" from upstream. (Also nothing new in Fedora http://pkgs.fedoraproject.org/gitweb/?p=bash.git regarding this issue).

FYI, looks like the upstream ML archives have been restored (no resolution for this bug yet, though).

Looks like they found a solution https://qa.mandriva.com/show_bug.cgi?id=61635#c9

CC: (none) => lihamakaroonilaatikko

(In reply to comment #7)
> Looks like they found a solution
> https://qa.mandriva.com/show_bug.cgi?id=61635#c9

No, that's a totally different issue/bug.

Ok. I'll make new bug for it.

(In reply to comment #9)
> Ok. I'll make new bug for it.

But it'll be closed as invalid, since Mageia doesn't package Adobe Reader....

Yeah, I figured that out after finding that file causing the problem was not from any rpm package.

This is now documented in the Errata: http://www.mageia.org/wiki/doku.php?id=mageia1:errata#bash_change_in_behaviour_when_expanding_environment_variables_when_using_tab_completion

Upstream has a patch: http://lists.gnu.org/archive/html/bug-bash/2011-03/msg00235.html

it can't be included ATM as a) we're in freeze and b) upstream doesn't think it's "the 90% solution".
(just in case you're interested in patch bash locally).

Upstream is still working on it

http://lists.gnu.org/archive/html/bug-bash/2011-09/msg00007.html

And some users are happy with the tested patch

http://lists.gnu.org/archive/html/bug-bash/2011-09/msg00046.html

CC: (none) => m.van.waes

any news?

(In reply to comment #15)
> any news?

Our version of bash is the latest one, and it's not fixed there in upstream. Either we wait or we apply an ad-hoc patch that fixes the problem. Can anyone recommend anything?

Regards,

-- Shlomi Fish

Upstream seems to have a good fix now:

http://lists.gnu.org/archive/html/bug-bash/2012-03/msg00023.html

Has it not yet been included, or do I misunderstand?:

http://git.savannah.gnu.org/cgit/bash.git/?h=direxpand

@ Shlomi

Since no one recommended anything here after you asked for it three months ago, if you'd still like a recommendation: maybe try on the Mageia-dev ml?

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

In Mageia 2 too.

Keywords: NEEDINFO => (none)
Version: Cauldron => 2

Hi all,

as noted here:

http://askubuntu.com/questions/41891/bash-auto-complete-for-environment-variables

This can be fixed by doing «shopt -s direxpand», which makes it expand directories again. You can put it in .bashrc .

Since there's an easy workaround for it, can we close this bug?

Regards,

-- Shlomi Fish

Sorry, but this bug saw no action since over 2 yrs ago. 
No cauldron package has stayed the same since then.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

Status: NEW => RESOLVED
Resolution: (none) => OLD