From: L A Walsh <cygwin@tlinx.org>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com, Alvin Seville <alvinseville7cf@gmail.com>
Subject: Re: Cygwin doesn't handle SIGWINCH properly in Windows Terminal
Date: Sun, 14 Feb 2021 12:44:32 -0800 [thread overview]
Message-ID: <60298BB0.1070301@tlinx.org> (raw)
In-Reply-To: <20210214174358.f828f285a566846254c3c54a@nifty.ne.jp>
On 2021/02/14 00:43, Takashi Yano via Cygwin wrote:
> This is because cygwin console handles SIGWINCH when the input
> messages is processed. If the process does not call either read()
> or select(), SIGWINCH will not be sent. This is the long standing
> problem of the implementation and hard to fix.
>
> ....
>
> This seems to be a bug of console code. I will submit a patch
> for this issue.
>
---
I'd be careful 'fixing' this, as it seems to work the same
way on linux / bash.
I have this func setup on bash_profile & bashrc on
both cygwin and linux:
# display new size of terminal when resized
:
showsize () {\
declare s=$(stty size); s="(${s// /x})" ;\
printf "%s" "$s${s//?/$'\b'}" ;\
}; export -f showsize
trap showsize SIGWINCH
-----
Of note, on linux, I didn't have to reset LINES/COLUMNS,
however, on cygwin, I note that I should.
Oh well -- hmmm....is that a bug?
next prev parent reply other threads:[~2021-02-14 20:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 10:39 Alvin Seville
2021-02-13 17:38 ` Brian Inglis
2021-02-14 8:43 ` Takashi Yano
2021-02-14 20:44 ` L A Walsh [this message]
2021-02-15 0:05 ` Takashi Yano
2021-02-16 2:17 ` L A Walsh
2021-02-16 5:48 ` Marco Atzeri
2021-02-16 6:20 ` Brian Inglis
2021-02-16 10:26 ` Thomas Wolff
2021-02-16 10:38 ` Thomas Wolff
2021-02-16 21:55 ` L A Walsh
2021-02-15 0:21 ` Takashi Yano
2021-02-16 10:31 ` Takashi Yano
2021-02-16 11:31 ` Takashi Yano
2021-02-16 16:26 ` Brian Inglis
2021-02-16 20:37 ` Takashi Yano
2021-02-16 20:50 ` Thomas Wolff
2021-02-16 22:11 ` Brian Inglis
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=60298BB0.1070301@tlinx.org \
--to=cygwin@tlinx.org \
--cc=alvinseville7cf@gmail.com \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).