Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh eats 100% CPU with completion in /
- X-seq: zsh-workers 27328
- From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: zsh eats 100% CPU with completion in /
- Date: Sun, 01 Nov 2009 18:31:55 +0000
- In-reply-to: Message from Mikael Magnusson <mikachu@xxxxxxxxx> of "Sun, 01 Nov 2009 02:50:14 +0100." <237967ef0910311850p2994c4e2ha72944842bc6fa8@xxxxxxxxxxxxxx>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
Mikael Magnusson wrote:
> (gdb) print clwpos
> $8 = 0
> (gdb) print clwords
> $9 = (char **) 0x8144278
> (gdb) print clwords[0]
> $10 = 0x82fb758 ""
Thanks---I think that means somehow it's got confused in the lexical
analyser, there's not much scope for more problems in get_comp_string().
That first word obviously ought to be "./x". Possibly something hasn't
been reset properly after the last operation; we've seen a couple of
things like that. We need to find out why the first
zshlex(), and hence gettok(), is setting tok to STRING but not tokstr to
"./x" (if it is, the problem is in get_comp_string() after all). It
might well be something quite simple.
--
Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
Messages sorted by:
Reverse Date,
Date,
Thread,
Author