Re: Problem with completion matching control

[opk@thoth.u-net.com (Oliver Kiddle)]

On Feb 18, 10:05am, Sven Wischnowsky wrote:

> Hm, still can't reproduce this. Do you still get the behavior (for the 
> other: completion after `t' and `te' behaved differently) with all
> recent patches: the completion option cleanup from 5399 with it's
> followup 5407 and the patch I sent yesterday in 5412?

I've just tested it with pws-9 and the problem has gone so one of those
patches must have fixed it. Thanks.

There seems to be a few problems with the completeinword option though.
Could someone offer a better explanation of what completeinword does
than the documentation gives. I think that when I first configured zsh,
I assumed that it allowed zsh to be more intelligent when completing
with the cursor in the middle of the line so I set it.

With autocd and completeinword set and the compctl MATCH 'm:{a-z}={A-Z}'
from the zsh source directory, if I type 
./co<tab>
I get completion working but it gets stuck on ./Config/. Is this a bug
or what is intended by completeinword.

I also tested out your fix for the matching control which prevents *
mapping to the anchor so ncftp sunsite.d<tab> works as I had wanted. I
found the following which I think is a bug:

zsh -f
setopt completeinword
compctl -x 'p[1]' -k '(a.b.c a.c.b)' -M 'r:|.=*  r:|=*' -- t
t a.<tab><tab><tab>

The above will complete to a.b.c, having never listed the alternatives.
It works as I would expect when completeinword is not set.

I also get the following which is certainly worse:

First three commands same as above
t a..c<left><left><tab>
Gives me: zsh: 4013 segmentation fault
With completeinword unsetopted, this works fine.

Anyway, I now have completeinword unsetopted in my setup so it isn't
bothering me.

Oliver Kiddle