Possible bug in completion?

Possible bug in completion?

[Alan Third]

I'm using the debian zsh-beta package:
zsh 4.1.0-dev-4 (i686-pc-linux-gnu)

and I came across this little thing...

If I type something like:

for FILE in /v/o/in/so<tab>


Then that completes to:

for FILE in /var/oscar/incoming/sounds/


Which is right. But if I try and do the same thing again zsh seg
faults. I tried using zsh -f, and once compinit is loaded the above
still occurs:

grover:/home/alan>zsh -f                
grover% autoload -U compinit
grover% compinit
grover% for FILE in /var/oscar/incoming/sounds/* ;do;done
grover% for FILE in /v/o/in/sozsh: segmentation fault  zsh -f

If it's any help, /var/oscar is mounted using nfs from a remote
machine...
-- 
Alan Third

Re: Possible bug in completion?

[Bart Schaefer]

On Wed, 29 May 2002, Alan Third wrote:

> [Do a completion and then] if I try and do the same thing again zsh seg
> faults.

zsh-workers/16776 was a patch for this, I think.

Re: Possible bug in completion?

[Alan Third]

On Tue, May 28, 2002 at 05:29:49PM -0700, Bart Schaefer wrote:
> On Wed, 29 May 2002, Alan Third wrote:
> 
> > [Do a completion and then] if I try and do the same thing again zsh seg
> > faults.
> 
> zsh-workers/16776 was a patch for this, I think.
Thanks! :)
-- 
Alan Third

RE: Possible bug in completion?

[Borsenkow Andrej]

> On Tue, May 28, 2002 at 05:29:49PM -0700, Bart Schaefer wrote:
> > On Wed, 29 May 2002, Alan Third wrote:
> >
> > > [Do a completion and then] if I try and do the same thing again
zsh seg
> > > faults.
> >
> > zsh-workers/16776 was a patch for this, I think.
> Thanks! :)

Which reminds me - there were some number of (completion) fixes
recently, some of them I'd like to see in 4.0 - if we are going to see
4.0.5 at all :-) Probably 4.2 would make sense as well. Either we need
some defined goals to achieve or just let's release it with all current
bells and whistles. 

-andrej