zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Andrew Owen <andrew.owen@principlestudios.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Strange terminal resizing behavior on macOS 11.6 and calling pwsh under zsh
Date: Wed, 6 Oct 2021 18:03:18 -0700	[thread overview]
Message-ID: <CAH+w=7bpeneYSNyETL3kwZhMHxkxUnaYSSSDPDkNAjYCBxAU2g@mail.gmail.com> (raw)
In-Reply-To: <7CE5FEA4-52A2-478B-98E4-1C30F5D6C2CF@principlestudios.com>

On Wed, Oct 6, 2021 at 4:06 PM Andrew Owen
<andrew.owen@principlestudios.com> wrote:
>
> I seem to have found a curious bug in how zsh interacts with pwsh on macOS 11.6. I first reported it to the pwsh team, here: https://github.com/PowerShell/PowerShell/issues/16174

I presume we can ignore the typo in
https://github.com/PowerShell/PowerShell/issues/16174#issuecomment-934715868
("/usr/local/bin pwsh ...").

"Process exited 130" normally means that a QUIT signal was received
somehow.  Zsh itself ignores QUIT but restores the default behavior
when starting a subprocess, unless that signal has been explicitly
ignored (here I assume the MacOS zsh is built with POSIX_SIGNALS
defined).  The handling of INT and QUIT also changes when the zsh
MONITOR option is not set, which typically happens when zsh is not
interactive (as with #! it is not because it's running a script file).

I would suggest two things:
1) Examine the pwsh process with dtruss while attempting to reproduce
the issue, to give some hint of whether QUIT is actually being
received.  Maybe you can figure out from where.
2) Try using "exec /usr/local/bin/pwsh ..." in the script so the zsh
parent is removed from the process tree, and then try to reproduce the
issue.


  reply	other threads:[~2021-10-07  1:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-06 23:05 Andrew Owen
2021-10-07  1:03 ` Bart Schaefer [this message]
2021-10-07  1:44   ` Andrew Owen
2021-10-07  2:51     ` Bart Schaefer
2021-10-07  2:58       ` Andrew Owen

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='CAH+w=7bpeneYSNyETL3kwZhMHxkxUnaYSSSDPDkNAjYCBxAU2g@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=andrew.owen@principlestudios.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).