[Top][All Lists]

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

Re: Filename completion BS-quotes variable references

From: Chet Ramey
Subject: Re: Filename completion BS-quotes variable references
Date: Wed, 21 Mar 2012 20:32:04 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2

On 3/21/12 5:37 PM, address@hidden wrote:

> Bash Version: 4.2
> Patch Level: 10
> Release Status: release
> Description:
>       Filename completion, typically by use of <tab>, causes variable 
> references in the typed path to be backslash-quoted, i.e. a backslash is 
> inserted before the '$'.  This does not occur when no completion matches were 
> found, but rather when matches were found.  This changes the meaning of the 
> command line and, among other things, prevents a double-<tab> from displaying 
> possible completions.
>       In bash 4.0, the variable was expanded instead.
>       Note that in the simplest form, the /etc/bash_completion file is not 
> involved.

There has been extensive discussion of this issue.

Look at http://git.savannah.gnu.org/cgit/bash.git/log/?h=direxpand for a
version of bash-4.2.24 with the changes described most recently in


Those changes address all of the bash-4.2 problems discussed and add a
shell option to revert to the bash-4.1 behavior.

That message has links to earlier discussions.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

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