zsh-workers
 help / color / mirror / code / Atom feed
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
Date: Sat, 24 Oct 2015 20:56:08 +0000	[thread overview]
Message-ID: <20151024205608.GE11372@tarsus.local2> (raw)
In-Reply-To: <CA+cBnHCFJYxvaLL4O7wmKwP7rcdoTrh5aViMkT6zZW3eYaWYjw@mail.gmail.com>

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


  reply	other threads:[~2015-10-24 20:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 16:15 Nir Friedman
2015-10-24 20:37 ` Daniel Shahaf
2015-10-24 20:45   ` Nir Friedman
2015-10-24 20:56     ` Daniel Shahaf [this message]
2015-10-24 21:04       ` Nir Friedman
2015-12-02  6:02         ` Nir Friedman
2015-12-02  8:39           ` Bart Schaefer
2015-12-02  9:24           ` Peter Stephenson
2015-10-25 16:07     ` Jun T.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151024205608.GE11372@tarsus.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=quicknir@gmail.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).