Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Reverting the effect of 'setopt nomonitor' executed during shell startup
- X-seq: zsh-users 27473
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Roman Perepelitsa <roman.perepelitsa@xxxxxxxxx>
- Cc: Andreas Hartmann <hartan@xxxxx>, Zsh Users <zsh-users@xxxxxxx>
- Subject: Re: Reverting the effect of 'setopt nomonitor' executed during shell startup
- Date: Fri, 14 Jan 2022 09:26:17 -0800
- Archived-at: <https://zsh.org/users/27473>
- In-reply-to: <CAN=4vMp7segBg5wwx46dzyZdC_ZV-ENoZ63dvvzZYbwVjmytZg@mail.gmail.com>
- List-id: <zsh-users.zsh.org>
- References: <6886b4278c2d2ce627ce3e48bd9d3034e5f66e78.camel@7x.de> <CAN=4vMp7segBg5wwx46dzyZdC_ZV-ENoZ63dvvzZYbwVjmytZg@mail.gmail.com>
On Fri, Jan 14, 2022 at 6:27 AM Roman Perepelitsa
<roman.perepelitsa@xxxxxxxxx> wrote:
>
> % >test.zsh <<\END
> zsh -fic "unsetopt monitor"
> stty icanon
> END
More interesting is that if that is changed to
% >test.zsh <<\END
zsh -fic "unsetopt monitor"
setopt monitor
stty icanon
END
then stty is still stopped by TTOU but zsh is not and waits forever for it.
Move the "setopt monitor" into the -c argument (after the unsetopt)
and the whole script stops with TTOU again. So it has something to do
with order of operations at startup.
I'm traveling today and can't look into it any further.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author