From: Alvin Seville <alvinseville7cf@gmail.com>
To: cygwin@cygwin.com
Subject: Cygwin doesn't handle SIGWINCH properly in Windows Terminal
Date: Sat, 13 Feb 2021 20:39:39 +1000 [thread overview]
Message-ID: <CABPP8W9h=LzUGf=JP-2x3SjrBPh8NJuoRbXzRU94b-WfBt94yw@mail.gmail.com> (raw)
Windows build number: Win32NT 10.0.19042.0 Microsoft Windows NT 10.0.19042.0
Windows Terminal version (if applicable): 1.5.10271.0
Script to reproduce this issue:
#!/usr/bin/env bashfunction outputText()
{
local text=$1
local -i textLength=${#text}
local -i line="$(tput lines) / 2"
local -i col="$(tput cols) / 2 - $textLength / 2"
clear
echo -en "\e[$line;${col}H$text"
}
trap "outputText 'Hello world!'" SIGWINCH
outputText 'Hello world!'while truedo
:done
As you see Windows Terminal doesn't handle SIGWINCH
<https://man7.org/linux/man-pages/man7/signal.7.html> properly. However
everything works fine when I execute my script directly from Cygwin
Terminal without Windows Terminal which users told
<https://github.com/microsoft/terminal/issues/9113#issuecomment-777703560>
me that it seems to be a Cygwin bug.
--
alvinseville7cf@Alvins-MacBook-Pro ~ $* echo *"Best regards, Alvin Seville."*
&& exit*
next reply other threads:[~2021-02-13 10:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 10:39 Alvin Seville [this message]
2021-02-13 17:38 ` Brian Inglis
2021-02-14 8:43 ` Takashi Yano
2021-02-14 20:44 ` L A Walsh
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='CABPP8W9h=LzUGf=JP-2x3SjrBPh8NJuoRbXzRU94b-WfBt94yw@mail.gmail.com' \
--to=alvinseville7cf@gmail.com \
--cc=cygwin@cygwin.com \
/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).