What does `works' mean here,
It means to work like "compgen -c pin", or like
_completion_loader ping; COMP_WORDS=(ping); COMP_CWORD=1;
_known_hosts; declare -p COMPREPLY
or somehow else get possible completion results.
and what are you trying to do with this patch?
I am trying to provide "pc
On 10/8/19 1:30 PM, Му��gnu.org wrote:
> Hello!
>
> I am unable to use "compgen -F" and made a patch to make it works.
What does `works' mean here, and what are you trying to do with this
patch?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita br
On 12/13/09 5:07 AM, Freddy Vulto wrote:
> `compgen -f' produces no output if the directory contains a single quote.
> I get the same result on both bash-3.2.39 and bash-4.0.35.
>
> Steps to reproduce the problem:
>
> $ mkdir a\'b
> $ touch a\'b/{c,d}
> $ compgen -f a\'b/
> $
>
>
On 091213 08:34, DennisW wrote:
Thanks for testing. Indeed on bash-4 quoting works for me as well. Adding
additional backslashes works also on bash-4:
$ echo $BASH_VERSION
4.0.35(2)-release
$ ls a*b # Make sure there's no `ab' directory
ls: cannot access a*b: No such file or dir
On Dec 13, 8:17 am, Freddy Vulto wrote:
> On 091213 05:13, DennisW wrote:
>
> > However, with quoting, these work:
>
> > compgen -f "a\'b/"
> > compgen -f 'a\"b/'
>
> > or using a variable:
>
> > dir="a\'b/"; compgen -f $dir
>
> Both do not work at my machine? Are you sure you don't have a direct
On 091213 05:13, DennisW wrote:
> However, with quoting, these work:
>
> compgen -f "a\'b/"
> compgen -f 'a\"b/'
>
> or using a variable:
>
> dir="a\'b/"; compgen -f $dir
Both do not work at my machine? Are you sure you don't have a directory
`ab' besides `a\'b'? That's whap happened to me to
On Dec 13, 4:07 am, Freddy Vulto wrote:
> `compgen -f' produces no output if the directory contains a single quote.
> I get the same result on both bash-3.2.39 and bash-4.0.35.
>
> Steps to reproduce the problem:
>
> $ mkdir a\'b
> $ touch a\'b/{c,d}
> $ compgen -f a\'b/
> $
>
> Ex
