Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zpty intermediate zsh process?
- X-seq: zsh-workers 47927
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Greg Klanderman <gak@xxxxxxxxxxxxxx>
- Cc: Zsh list <zsh-workers@xxxxxxx>
- Subject: Re: zpty intermediate zsh process?
- Date: Sat, 6 Feb 2021 13:53:13 -0800
- Archived-at: <https://zsh.org/workers/47927>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-workers/2021-02/CAH%2Bw%3D7YNN4JL6jUOUeWxojd%2BHsdVDRa8%3DUUU_JCrA-De34auDQ%40mail.gmail.com>
- In-reply-to: <24606.56852.904076.773054@lwm.klanderman.net>
- List-id: <zsh-workers.zsh.org>
- References: <24606.56852.904076.773054@lwm.klanderman.net>
On Sat, Feb 6, 2021 at 10:21 AM Greg Klanderman <gak@xxxxxxxxxxxxxx> wrote:
>
> I can prefix the command with 'exec' to avoid that, but looking at the
> code in zpty.c, maybe the execode() call should just be setting the
> (third) 'exiting' argument to true?
That doesn't seem to cause any of the tests to fail, but I wonder
about side effects when traps are enabled, especially the EXIT trap.
Maybe just passing !sigtrapped[SIGEXIT] as the third argument would
suffice ... or maybe the handling of that trap by zpty is already
iffy.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author