Re: make history-complete-older do nothing on empty string

[Peter Stephenson <p.stephenson@samsung.com>]

On Wed, 18 Apr 2018 07:21:35 +0200
Vincent Bernat <bernat@luffy.cx> wrote:

> Hey!
> 
> I sometime hit M-/ by error and this invokes history-complete-older
> which then blocks when the current word is empty and it takes me 5-10
> seconds to be able to "kill" it. Is there a way to teach this function
> to not complete anything on empty (or one-char) input?
> 
> Thanks!

I don't think that's a normal effect.

You can try and debug it this way:


_debug_history() {
  _complete_debug _history_complete_word
}
debug_history .complete-word _debug_history
bindkey '^[/' _debug_history


Then when you use the command you should get a log of what it was doing,
though if you have to abort you may well find you have to look for the
most recently created file in /tmp to discover what that was.  If
you get anything, post the result.

pws