Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: _history-complete-older buggy
- X-seq: zsh-workers 26082
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers <zsh-workers@xxxxxxxxxx>
- Subject: Re: _history-complete-older buggy
- Date: Sun, 23 Nov 2008 10:37:22 -0800
- In-reply-to: <237967ef0811230401j7bcceb0bg5e68b95483c344bf@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <237967ef0811230401j7bcceb0bg5e68b95483c344bf@xxxxxxxxxxxxxx>
On Nov 23, 1:01pm, Mikael Magnusson wrote:
}
} If i type a * and press _history-complete-older, i get this output
My guess is that this is going to be another case of some setting that
you use that is going to need turning off in _comp_options, or the
like. Yep, I can duplicate your error if I "setopt glob_complete".
} and after waiting maybe 15-20 seconds, it does give some set of
} completions that do and do not start with a *. It might simply be all
} words in my history.
It almost certainly is. You've asked for globbing completion, so the
* is being interpreted as a pattern, and guess what it matches?
What's your HISTSIZE setting?
The completion is in fact scanning the $historywords array, which is
all words in your history, so the more enormous your history compared
to the amount of memory and processor speed you have, the more poorly
this completion is going to behave.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author