From: Andrey Repin <anrdaemon@yandex.ru>
To: Kacper Michajlow <kasper93@gmail.com>, cygwin@cygwin.com
Subject: Re: Suspend doesn't work in cmd
Date: Tue, 19 May 2020 17:15:31 +0300 [thread overview]
Message-ID: <1238835926.20200519171531@yandex.ru> (raw)
In-Reply-To: <CABPLASTGXFXphswEPq+8PNTb_5Y_LwrPBwPvvQ_t5597C7XK4w@mail.gmail.com>
Greetings, Kacper Michajlow!
> On Mon, 18 May 2020 at 05:06, Takashi Yano wrote:
>> On Sun, 17 May 2020 19:57:15 +0200
>> Kacper Michajlow 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.
>>
> Thanks for explanation. I report those bugs, because I kind of hope to get
> away from mintty and use something like Windows Terminal for all envs. But
> it doesn't look feasible for Cygwin.
Why not use mintty instead? :D
--
With best regards,
Andrey Repin
Tuesday, May 19, 2020 17:15:05
Sorry for my terrible english...
prev parent reply other threads:[~2020-05-19 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 17:57 Kacper Michajlow
2020-05-18 3:05 ` Takashi Yano
2020-05-19 10:54 ` Kacper Michajlow
2020-05-19 14:15 ` Andrey Repin [this message]
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=1238835926.20200519171531@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=kasper93@gmail.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).