Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: yet another match-spec-cursor bug
- X-seq: zsh-workers 11155
- From: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: PATCH: yet another match-spec-cursor bug
- Date: Thu, 4 May 2000 16:52:26 +0200 (MET DST)
- In-reply-to: Sven Wischnowsky's message of Wed, 3 May 2000 10:51:11 +0200 (MET DST)
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
I wrote:
> Felix Rosencrantz wrote:
>
> ...
>
> > If I try completing "bui", I rarely I get only "build" or more often I get the
> > following sequence after hitting tab:
> > bui --> build.out[] --> build[.]out --> build.out[] --> build.out1[]
> > --> build.out2[]
> >
> > Most times I get the correct behavior. Though within several attempts I get
> > the
> > described incorrect behavior.
>
> That's bad news: not always repeatable. I've tried it for quite some
> time now and still can't reproduce it. I'll continue to try...
>
> The fact that you don't always get it makes me think that it may be a
> problem with an not-initialised variable or memory block. Do you have
> configured with mem-debug?
>
> What really irritates me is that it doesn't go into menu-completion on
> the second TAB. Hm.
I've now tried it on DU 4.0 and Linux, both with and without mem-debug
and still can't reproduce it. Does anyone else see this behaviour?
I'm not even completely sure where to look when trying to debug this...
Bye
Sven
--
Sven Wischnowsky wischnow@xxxxxxxxxxxxxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author