Hello Gordon,
On Thu, 30 Aug 2018 15:00:41 -0700 Gordon Messmer
wrote:
> On 08/30/2018 01:11 AM, wwp wrote:
> > I well know that to match "1.foo-named", I should use `ls*foo*`
> > (trailing *) and I'm sure that you know that `ls *foo` matches
> > 1.foo.
>
>
> I didn't. Given a better
On 08/30/2018 01:11 AM, wwp wrote:
I well know that to match "1.foo-named", I should use `ls*foo*`
(trailing *) and I'm sure that you know that `ls *foo` matches
1.foo.
I didn't. Given a better description of what you're trying to do, I see
that the bash's behavior has changed.
I also
Hi Gordon,
On Wed, 29 Aug 2018 17:59:58 -0700 Gordon Messmer
wrote:
> On 08/29/2018 09:22 AM, wwp wrote:
> > On Wed, 29 Aug 2018 08:27:06 -0700 Gordon Messmer om> wrote:
> >> On 08/28/2018 11:33 PM, wwp wrote:
> >>>- it doesn't expand *foo whereas there are *foo-named files in curre
Hello Mark,
On Wed, 29 Aug 2018 15:20:45 -0700 (PDT) Mark Milhollan
wrote:
> On Wed, 29 Aug 2018, wwp wrote:
>
> >while bash completion was working great to me in CentOS6, since I'm
> >using C7 I spend my day stuck on completion not working the way it
> >should.
>
> Since you don't want
On 08/29/2018 09:22 AM, wwp wrote:
On Wed, 29 Aug 2018 08:27:06 -0700 Gordon Messmer
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
On Wed, 29 Aug 2018, wwp wrote:
>while bash completion was working great to me in CentOS6, since I'm
>using C7 I spend my day stuck on completion not working the way it
>should.
Since you don't want what it provides you can either remove the
bash-completions* packages or append "complete -r" to
Hello Gordon,
On Wed, 29 Aug 2018 08:27:06 -0700 Gordon Messmer
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.
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 single word, given a string that appears at
the beginning of a
Hello there,
while bash completion was working great to me in CentOS6, since I'm
using C7 I spend my day stuck on completion not working the way it
should.
The bad situations I'm facing are:
- it doesn't expand *foo whereas there are *foo-named files in current dir,
for instance:
# rm *foo
9 matches
Mail list logo
