Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: Bug Report: Interactive Mode Glitches

Hi Daniel,

My apologies, I only realized upon rereading this that I completely omitted
a description of what happened! What happens is that it crashes the zsh
process. So if you are running zsh by simply calling it from bash, it
reverts to the bash process. If (more typically) you are running the zsh
process directly in your terminal emulator, it crashes that window of the
terminal emulator.

I'm running the latest zsh, 5.1.1, but I've been observing this bug since

I have many things in my .zshrc, I am using prezto:
https://github.com/quicknir/prezto. However, I have duplicated the problem
in the past with a much more minimal setup, what I have below *should*
suffice. The problem is that I don't have a list of steps to reliably
duplicate it. Just use it for a while, keep typing and hitting backspace,
and at some point it goes off.

By interactive mode, I mean interactive menu completion mode in zsh. In
this mode after you hit tab (however many times), you will have a list of
possible completions that will automatically narrow as you type. It's
activated by this:

zstyle ':completion:*' menu select=0 interactive

I'm not sure if zsh is killed by signal or some other mechanism.



On Sat, Oct 24, 2015 at 4:37 PM, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>

> Nir Friedman wrote on Fri, Oct 23, 2015 at 12:15:50 -0400:
> > I relatively often see bugs in zsh's interactive mode. I can't duplicate
> > them frequently, but the trigger is nearly always either: 1) hitting
> > backspace when already in interactive mode and incremental matching is
> > happening, or 2) hitting Ctrl-C in an attempt to exit from interactive
> mode.
> >
> What happens when you do these things, and what do you expect to happen?
> What version of zsh are you running?
> Is there anything else in your .zshrc?
> By 'interactive mode' do you mean Vi insert mode?
> > Here are some relevant settings:
> ...
> > I'm happy to try to provide more information, if someone can tell me how
> > (perhaps run zsh with some kind of debug flag, and look in there the next
> > time a crash happens?).
> What do you mean by 'a crash'?  Is zsh killed by a signal?
> Cheers,
> Daniel

Messages sorted by: Reverse Date, Date, Thread, Author