X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AAA6B387086C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1589771178;
	bh=GUhY2Jdc+uLOwjspdnBBkMnHx1/l78RCp7Rum/vrYcg=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=JU2IkC+7m3YGldClSERqHEHCmzLGmpP6Q4r1feDKgP8p8re+23Ji57snomz17a8hW
	 zDMN/N1Ewl4j2ec15uQ9AogLiEgQda9W0954OP75+77uhjIC8A72HAWloekawbrUGf
	 xqeh/lomDW6NWm3yjIisXaro+V1gQAPBEV5fNPgM=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 0A990386F447
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com 04I35Ufx016508
X-Nifty-SrcIP: [124.155.40.7]
Date: Mon, 18 May 2020 12:05:34 +0900
To: cygwin AT cygwin DOT com
Subject: Re: Suspend doesn't work in cmd
Message-Id: <20200518120534.97f3515d2295301421f585ae@nifty.ne.jp>
In-Reply-To: <CABPLASSNEJP7rC1q-L63kqDH1W71hUK1AkJ+OuW8sEWK+ycO1Q@mail.gmail.com>
References: <CABPLASSNEJP7rC1q-L63kqDH1W71hUK1AkJ+OuW8sEWK+ycO1Q AT mail DOT gmail DOT com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,
 SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <http://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <http://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On Sun, 17 May 2020 19:57:15 +0200
Kacper Michajlow via Cygwin <cygwin AT cygwin DOT com> wrote:
> Hi,
> 
> Control keys doesn't seem to be working correctly under cmd.
> 
> STR:
> 1. Run bash in cmd.exe
> 2. Run anything, in my case "seq 1 100000"
> 3. Try to suspend job with CTRL+Z or suspend printing with CTRL+S
> 
> Ii will ignore request. Works in mintty, doesn't in cmd.

Thanks for the report. This is a known problem, however,
it is hard to fix soon.

In current console implementation, ctrl-Z is processed in
read() system call. So, if process does not call read(),
ctlr-Z does not work.

You can confirm that ctrl-Z works for cat, od, etc. which
calls read().

One solution might be to introduce a thread to handle the
keystrokes. I wonder if it is worth enough to introduce such
a big modification for console code.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple