[Top][All Lists]

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

damaged behaviour for completion of words with variables

From: wiebittewas
Subject: damaged behaviour for completion of words with variables
Date: Sat, 17 Dec 2011 12:52:49 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv: Gecko/20110616 Lightning/1.0b2 Mnenhy/0.8.4 Thunderbird/3.1.11

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCO$
uname output: Linux dose 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7
14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 4.2
Patch Level: 10
Release Status: release

        typing 'echo $PWD/[TAB]' results in 'echo \$PWD/' instead of
        'echo <current-path>/'
        (all without single quotes of course...)

        This behaviour doesn't exist at least in bash-4.1.5

        ( bash-4.2.10 comes here with ubuntu-11.10,
          bash-4.1.5 comes here with ubuntu-10.04 )

        Copying old version of bash to new system brings right
        behaviour. If you think the new behaviour is right, then
        there should be an easy way, to revert it by an option,
        because at least for me bash-4.2.10 is unusable with this

        see above.

        revert to old behaviour or make it configurable at run-time

For questions or replies please use my eMail directly, because I'm
currently not reading any bug-lists for bash.

best regards


reply via email to

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