Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh eats 100% CPU with completion in /
- X-seq: zsh-workers 27329
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: zsh eats 100% CPU with completion in /
- Date: Sun, 01 Nov 2009 11:33:05 -0800
- In-reply-to: <200911011831.nA1IVtMH003055@xxxxxxxxxxxxxxxxxxx>
- 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
- References: <200911011831.nA1IVtMH003055@xxxxxxxxxxxxxxxxxxx>
On Nov 1, 6:31pm, Peter Stephenson wrote:
}
} 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".
Hmm. Somewhere in the completion system -- I forget now whether it's in
the C code (though I believe so) -- the string on the line is modified
to insert an "x" as a placeholder, which is then later deleted. I wonder
if something is going wrong there -- either the pointer isn't being
advanced properly when the "x" is inserted, or it's being decremented
incorrectly (or too often) when the "x" is removed?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author