Re: completion fails on file names with special characters

[Chet Ramey]

> That message is a reflection of where things currently are.  It contains a
> patch that will allow bash-completion to work unchanged.  (In a nutshell,
> bash-completion makes assumptions about what compgen will do with quoted
> null arguments that changed between bash-4.2 and bash-4.3.)
> 
> I think that patch will fix most, if not all, of the bash-completion
> problems.  I need people to test it, since the platforms I commonly use
> for development (Mac OS X, RHEL) do not install bash-completion.
> 
> For instance, I believe that the problem with these unquoted special
> characters is that they break words for readline, and readline passes
> an empty argument to the completion function as the word to be completed.
> I'm not sure what bash-completion does with that to make it include the
> previous word.

I've updated the patch, and attached it.  This seems to fix all of the
reported problems from Debian's version of bash-completion.  One thing
I have yet to do is to verify that other systems that ship bash-completion
have the same issues.  If I cannot replicate the Debian-reported issues
on those systems, I will most likely not release this as an official
patch.

Chet

pcomplete-dequote
Description: Text document

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