From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-36949-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 6362 invoked by alias); 24 Oct 2015 21:04:52 -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: 36949
Received: (qmail 16034 invoked from network); 24 Oct 2015 21:04:50 -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,FREEMAIL_FROM,
	HTML_MESSAGE,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0
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=ZQ+A+em5qCAAO08y2u90RmFmgily6zttYyuXbxgJBeA=;
        b=0oC54tUeuKfVgt7EwBqzaXTPlOZ5i0HEzUQSYsy4RCxnJakjBPgcwy8MUOETXj26x7
         zaEBueU2BORD/fkIKrJTwDuwQuWhxG2gs/CzosfssR0MQCfjLwxnIxlVvqId44G8hD0O
         +nOS6XHFzckhl1lGM782ira3HIiLtDYxyi4e0eIz+/1oyDGI+MVUoMVWi1lR2FjffVFS
         tt/AmWkkcF57Us29/uud5nRfII7XW9MWOuxDZ2FEMUWahVK7egUUj9qvZVSyvWdufebB
         c+9KXhen8Zm+RFqYeQIY+a37Hy2Qp43e5mJH15hHRNTMlbmv3g2gknydMSuYNS5DMpyc
         r9TQ==
X-Received: by 10.181.13.11 with SMTP id eu11mr12544273wid.10.1445720687228;
 Sat, 24 Oct 2015 14:04:47 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <20151024205608.GE11372@tarsus.local2>
References: <CA+cBnHDFZPK4d3hRYGZ_5o=1mep3D5iq67Ppsy1N91B9Pqd9vw@mail.gmail.com>
 <20151024203730.GD11372@tarsus.local2> <CA+cBnHCFJYxvaLL4O7wmKwP7rcdoTrh5aViMkT6zZW3eYaWYjw@mail.gmail.com>
 <20151024205608.GE11372@tarsus.local2>
From: Nir Friedman <quicknir@gmail.com>
Date: Sat, 24 Oct 2015 17:04:27 -0400
Message-ID: <CA+cBnHAazvWqfhoVthXNsS6rLef6jKkJk=OWhAX-Em09OC_eAA@mail.gmail.com>
Subject: Re: Bug Report: Interactive Mode Glitches
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Content-Type: multipart/alternative; boundary=f46d043c7de601befa0522e0149f

--f46d043c7de601befa0522e0149f
Content-Type: text/plain; charset=UTF-8

Yes, I run with a tabbed emulator (terminator) and just the one tab closes,
sorry that wasn't clear. I will try running zsh from inside zsh and see
what I come up with.

I'm mostly on FC20, but I've also observed this on recent Ubuntu versions.

On Sat, Oct 24, 2015 at 4:56 PM, Daniel Shahaf <d.s@daniel.shahaf.name>
wrote:

> 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
>

--f46d043c7de601befa0522e0149f--