From: Peter Stephenson <p.stephenson@samsung.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: SIGWINCH not respected when terminal size is unchanged
Date: Thu, 26 Jul 2018 17:10:28 +0100 [thread overview]
Message-ID: <20180726161029eucas1p2aeb514866d4bf28e900598dd9c6f7bfd~E9xIFUPGY0381603816eucas1p2w@eucas1p2.samsung.com> (raw)
In-Reply-To: <CAH+w=7anA7b4a2TshTezJscqsfUBeSKV9ZDWpUphX3UzpO6OrQ@mail.gmail.com>
On Thu, 26 Jul 2018 09:03:21 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Thu, Jul 26, 2018 at 6:42 AM, Sheheryar Parvaz
> <skipper308@hotmail.ca> 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
next prev parent reply other threads:[~2018-07-26 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 13:42 Sheheryar Parvaz
2018-07-26 16:03 ` Bart Schaefer
2018-07-26 16:10 ` Peter Stephenson [this message]
2018-07-26 16:36 ` Bart Schaefer
2018-07-27 1:33 Sheheryar Parvaz
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='20180726161029eucas1p2aeb514866d4bf28e900598dd9c6f7bfd~E9xIFUPGY0381603816eucas1p2w@eucas1p2.samsung.com' \
--to=p.stephenson@samsung.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).