Zsh Mailing List Archive
Messages sorted by:
Re: Bug Report: Interactive Mode Glitches
- X-seq: zsh-workers 36947
- From: Nir Friedman <quicknir@xxxxxxxxx>
- To: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- Subject: Re: Bug Report: Interactive Mode Glitches
- Date: Sat, 24 Oct 2015 16:45:23 -0400
- Cc: zsh-workers@xxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KXU7zEhPtueHbbrj4znAfvFyL28pg+ERxCcsQRpEQD0=; b=dIvbu6GwHX6xYVBazlRgLyDO+UR2Qqgg3Ns7r1iU5I1Dt4eZ7Kns8UhfWl/DdnisKt BPkOd33ItCpFXeS7d8VwqsHMeB/nQBJVRJabNQfHaPqw/OlV8npYpzhv7aRkkMwAU00Y PHWpHDCUu1RSksa1J0EjirCopFSO0Sr9Bfv5kWi9NS5l0t3BJotLFoXLx3+nRmFD8prt CAgD8Bpbdez68+mo0wjSCPGG5jBerh7B7Zth0HwIONf4usOYUlKLoBRQGYWBpHRRcFH7 PQZhKFOq+5Nvs+YW9Efz55URU7oNpLmaYm5sAQ7Q3B5NTVeESFnRlTRBk8cpGjLy+agN WV8Q==
- In-reply-to: <20151024203730.GD11372@tarsus.local2>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CA+cBnHDFZPK4d3hRYGZ_5o=1mep3D5iq67Ppsy1N91B9Pqd9vw@mail.gmail.com> <20151024203730.GD11372@tarsus.local2>
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
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
> 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?
Messages sorted by: