Displaying 3 results from an estimated 3 matches for "9880736fa3ce".
2018 Aug 29
2
bash completion in C7
Hello Gordon,
On Wed, 29 Aug 2018 08:27:06 -0700 Gordon Messmer <gordon.messmer at gmail.com> wrote:
> On 08/28/2018 11:33 PM, wwp wrote:
> > - it doesn't expand *foo whereas there are *foo-named files in current dir, for instance:
> > # rm *foo
> > will show nothing whereas there's a file barfoo in curdir.
>
> Tab completion finishes a
2018 Aug 30
0
bash completion in C7
...ords on the command line, usually so that you can remove some matches.
>>
>> Neither will do specifically what you're trying to do, as far as I know.? I think it's simply too ambiguous.
> This works fine in CentOS 6
$ docker run -i -t --rm centos:6 /bin/bash --login
[root at 9880736fa3ce ~]# touch 1.foo-named
[root at 9880736fa3ce ~]# touch 2.foo-named
[root at 9880736fa3ce ~]# ls *.fo
Tab completion doesn't work the way you're suggesting, on CentOS 6. It's
possible that such a feature exists in some shell, but not one that I'm
aware of.
2018 Aug 30
2
bash completion in C7
...t you can remove some matches.
> >>
> >> Neither will do specifically what you're trying to do, as far as I know.
> ? I think it's simply too ambiguous.
> > This works fine in CentOS 6
>
> $ docker run -i -t --rm centos:6 /bin/bash --login
> [root at 9880736fa3ce ~]# touch 1.foo-named
> [root at 9880736fa3ce ~]# touch 2.foo-named
> [root at 9880736fa3ce ~]# ls *.fo
>
> Tab completion doesn't work the way you're suggesting, on CentOS 6. It's possible that such a feature exists in some shell, but not one that I'm aware of.
Hah. Y...