From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-36948-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 17925 invoked by alias); 24 Oct 2015 20:56:12 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 36948
Received: (qmail 23126 invoked from network); 24 Oct 2015 20:56:12 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_DKIM_INVALID
	autolearn=ham autolearn_force=no version=3.4.0
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
	daniel.shahaf.name; h=cc:content-type:date:from:in-reply-to
	:message-id:mime-version:references:subject:to:x-sasl-enc
	:x-sasl-enc; s=mesmtp; bh=teeLaYROlALuEkZIapA6QZBTZPQ=; b=XSwGs9
	A4TJXOWijglhjTw8JmdWjPuF57ee0nLKBXCknR1OXU7pcD7awtS8Kg11SZ1/sxZy
	n1wMPgTfJ2r8Pj2+uBrk2yPDnYcSlkpZ9esUctS+M7ob77Nf+9hd6M5kTkQ5vdwA
	9O7QzXGI8ceOQhBQjMmOiDSooymJblLIZp18U=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
	messagingengine.com; h=cc:content-type:date:from:in-reply-to
	:message-id:mime-version:references:subject:to:x-sasl-enc
	:x-sasl-enc; s=smtpout; bh=teeLaYROlALuEkZIapA6QZBTZPQ=; b=NEz7Q
	t0D3V4gMsfPk9FNeVRUkNSqx+LPdG4e1uPqs1gygKwKNy9tDA6mXInOwy8exRG8C
	tutB8gQK7WuPohfP+H2YrwzrgD/XjdMtzQ8FyIZdlP1Vy+rO9sZutgncsMqO176L
	y/+25C+AhY7icumGrz72sUY3l0B/S10UZ78lZU=
X-Sasl-enc: fTYVe0R/xxDPv/whpQf40ZBwS/T951EnqxTqwtNEaTp9 1445720170
Date: Sat, 24 Oct 2015 20:56:08 +0000
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Nir Friedman <quicknir@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: Bug Report: Interactive Mode Glitches
Message-ID: <20151024205608.GE11372@tarsus.local2>
References: <CA+cBnHDFZPK4d3hRYGZ_5o=1mep3D5iq67Ppsy1N91B9Pqd9vw@mail.gmail.com>
 <20151024203730.GD11372@tarsus.local2>
 <CA+cBnHCFJYxvaLL4O7wmKwP7rcdoTrh5aViMkT6zZW3eYaWYjw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+cBnHCFJYxvaLL4O7wmKwP7rcdoTrh5aViMkT6zZW3eYaWYjw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

Nir Friedman wrote on Sat, Oct 24, 2015 at 16:45:23 -0400:
> 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.
> 

What probably happens is not that the terminal emulator crashes, but
that it closes because the shell exited (abnormally).  Try instructing
the terminal emulator to remain open after the process in the pty exits
(such as with tmux's remain-on-exit option), or using a tabbed terminal
emulator, to see this.

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

Try running zsh from another zsh instance.  If the nested zsh crashes,
the outer zsh will tell you that:

    % zsh
    tarsus% kill -11 $$ 
    [1]    17214 segmentation fault  zsh
    % echo $?
    137

I'm not sure what to say about the rest of your email, so I'll leave it
to others on list.  Incidentally, what OS / distro are you on?

Cheers,

Daniel