[Top][All Lists]

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

Re: Bug#740971: completion fails on file names with special characters

From: Chet Ramey
Subject: Re: Bug#740971: completion fails on file names with special characters
Date: Thu, 27 Mar 2014 20:11:04 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0

On 3/27/14, 7:11 PM, Uwe Storbeck wrote:
> On Mar 27, Chet Ramey wrote:
>> Since that line, as you entered it above, is a syntax error, it's not
>> clear what bash should do with it (probably nothing).  What do you
>> expect to happen?
> The same as if you would try to complete any non-existing file
> name, nothing? The completion should not append an "a" to the
> typed in "a(". Instead the cursor should stay in the same
> position (after the parenthesis) and bash should beep.

Yes, if bash can detect a syntax error, that's probably the best

> When you try to complete "ls ab" with <TAB> in the same example
> with the two files "aa" and "a(" in a directory bash-completion
> handles it correctly. It only fails because of the parenthesis
> (and maybe also with other special characters).

There is virtually nothing common between the two cases other than
the fact that they are two-character strings beginning with `a'.
This has nothing to do with bash-completion (maybe I should remove
the debian bug address from the recipients).

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