[Top][All Lists]

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

Re: bash completion escaping bug

From: Chet Ramey
Subject: Re: bash completion escaping bug
Date: Tue, 25 Aug 2015 11:01:08 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0

On 8/24/15 4:01 PM, Neven Sajko wrote:
> Hi,
> I use bash 4.3.039 and there is a bug (not necessarily a recent
> regression) with its file name completion feature.
> for example I have this in shell input:
>   db.rc $home/Downloads/games/DOS/Captai
> and after I press Tab I have this:
>   db.rc \$home/Downloads/games/DOS/Captain\ Bible\ in\ the\ Dome\ of\
> Darkness.zip
> Notice the dollar sign which is now erroneously escaped (home is a variable).

This is a case for which you need to enable the `direxpand' option.  You've
presented the bash completion code with an ambiguous case: it needs to
backslash-escape characters in the filename that are special to the shell,
but you want some of them to be escaped (the spaces) and not others (`$').
The bash interface to the readline completion engine escapes all special
characters in the filename, and, without `direxpand', the filename it's
presented looks like this:

$home/Downloads/games/DOS/Captain Bible in the Dome of Darkness.zip

The quoted version is what you see.

Enabling `direxpand' will eliminate the ambiguity by expanding the
variable to its value before trying to quote the special characters.

``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]