* Chet Ramey <[EMAIL PROTECTED]> [2008-03-18 00:22]:
>> I'd like to know if it is possible to change the options of the
>> programable completion within the completion function.
>
> Not currently. I'm thinking about a new builtin that would accept the
> same set of -o options as complete/compgen (
* Chet Ramey <[EMAIL PROTECTED]> [2008-03-17 22:57]:
>> Can you elaborate on the differences in case they're the cause of other
>> strange behaviours?
>
> 1. Backslashes should not be stripped within single quotes.
>
> 2. Backslashes should only be stripped within double quotes if they're
> f
* Chet Ramey <[EMAIL PROTECTED]> [2008-03-17 18:47]:
> For historical reasons, complete/compgen dequote the filename they're
> passed, removing backslash escapes and interpreting embedded quoted
> substrings.
Yes. I've run into this problem now several times while trying to fix
the bugs in bash_co
Hi,
I'm currently working on the bash-completion package for Debian/Ubuntu.
I'd like to know if it is possible to change the options of the
programable completion within the completion function.
An example would be to allow environment variables in place of
filenames. But if I set -o filenames,
Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
