[Top][All Lists]

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

Re: bash tab variable expansion question?

From: John Embretsen
Subject: Re: bash tab variable expansion question?
Date: Mon, 11 Jun 2012 09:59:42 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1

On 27 Feb 2011 18:18:24 -0500, Chet Ramey wrote:
>> On Sat, Feb 26, 2011 at 10:49 PM, gnu.bash.bug <address@hidden>wrote:
>> A workaround is fine but is the 4.2 behavior bug or not?
>It's a more-or-less unintended consequence of the requested change Eric
>Blake referred to earlier in the thread.



> The question is how to tell readline that the `$' should be quoted
> under some circumstances but not others.  There's no hard-and-fast
> rule that works all the time, though I suppose a call to stat(2)
> before quoting would solve part of the problem.  I will have to give
> it more thought.
> Chet

Any updates on this issue?

The workarounds for $PWD and $OLDPWD is not enough, and the "workaround" of going back on the command line and removing escape characters is not acceptable in my humble opinion.

I often use environment variable-based tab completion to navigate to the correct directory on my system, but with bash 4.2 this is no longer an option. For example,

with CODE=/path/to/dir and /path/to/dir/ containing test1/ and test2/,

cd $CODE/test<TAB><TAB> should give a list of $CODE/test1 $CODE/test2 when those directories exist, not "cd \$CODE/test".

If there is no fix in sight for this issue, can someone point me to a guide for downgrading bash in recent popular Linux distros?



reply via email to

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