Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: SIGWINCH not respected when terminal size is unchanged
- X-seq: zsh-workers 43210
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: "zsh-workers@xxxxxxx" <zsh-workers@xxxxxxx>
- Subject: Re: SIGWINCH not respected when terminal size is unchanged
- Date: Thu, 26 Jul 2018 17:10:28 +0100
- Cms-type: 201P
- Dkim-filter: OpenDKIM Filter v2.11.0 mailout2.w1.samsung.com 20180726161031euoutp025b823a9ede2ce42c7d2d5c8ce63d430f~E9xJdbouX1735317353euoutp02O
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1532621431; bh=J8aiAQSPzbgCy+IonKP/ontWcuLBNXe2hPfSmo0M7V0=; h=Date:From:To:Subject:In-Reply-To:References:From; b=CCon4KMt4SjQCc7TecAijmBLxOkzywxO8KX3UXDo9u8l2FPmdJZwViO2/Uq/qlDW4 HqPcZWJcbPK/yy5FYPK7IWvzCj9/FidFzxoHz7vbw6fEg2lrV1ZGiNLUnfg6PYmzOy sZHuTzo7FD0UOV7ITAORLMXMAax4TLsMMNNKG9Ls=
- In-reply-to: <CAH+w=7anA7b4a2TshTezJscqsfUBeSKV9ZDWpUphX3UzpO6OrQ@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- Organization: SCSC
- References: <DM5PR13MB15968B3171AABDC584F234A3F12B0@DM5PR13MB1596.namprd13.prod.outlook.com> <CGME20180726160357epcas1p2181b00a27b876e42d91f861c8aee1633@epcas1p2.samsung.com> <CAH+w=7anA7b4a2TshTezJscqsfUBeSKV9ZDWpUphX3UzpO6OrQ@mail.gmail.com>
On Thu, 26 Jul 2018 09:03:21 -0700
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> On Thu, Jul 26, 2018 at 6:42 AM, Sheheryar Parvaz
> <skipper308@xxxxxxxxxx> wrote:
> > This breaks software such as abduco and dtach, as they call
> > SIGWINCH upon reattaching.
>
> Sorry, could you explain exactly what you mean by "not respected" and
> what breakage you observe?
>
> The signal is certainly always trapped, and zsh always checks that
> LINES and COLUMNS match the values returned by TIOCGWINSZ, so the only
> internal difference is whether a reset of the line editor occurs.
> Other processes are not blocked from receiving the signal. So what
> exactly is wrong?
I was going to ask that, but looking at the code I *suspect* that
the line's not being redrawn, which indeed doesn't happen if the
configuration didn't change. But this needs confirming.
If that's the case, I'm wondering if there's a reason why the code's
like that --- didn't we have to deal with floods of SIGWINCHs causing
havoc at one point?
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author