From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: 3.1.x: Mangled input/output when calling non-cygwin programs
Date: Sun, 09 Feb 2020 13:42:00 -0000 [thread overview]
Message-ID: <20200209224223.fd1e411ec7255dd631ba2843@nifty.ne.jp> (raw)
In-Reply-To: <20200202185909.a3b3f8627438177e18171de3@nifty.ne.jp>
On Sun, 2 Feb 2020 18:59:09 +0900
Takashi Yano wrote:
> On Sat, 1 Feb 2020 19:00:04 +0100
> m0viefreak wrote:
> > 3) Typed characters while non-cygwin program is running are lost.
> > Usually, when typing characters while a native program executes,
> > which does *not* read from standard input, after the program exits,
> > all these typed characters are put into the prompt.
> > When executing a non-native program, such as, again, "mvn clean",
> > which does not read from stdin, typed characters are completely lost.
> > This is very frustrating, since I am often quicker at tying the
> > next command, while the previous command is still doing something.
>
> I know the cause of this problem. Let me consider.
I will submit a patch for this issue shortly.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2020-02-09 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 18:00 m0viefreak
2020-02-02 9:59 ` Takashi Yano
2020-02-02 12:18 ` m0viefreak
2020-02-02 19:01 ` Takashi Yano
2020-02-03 14:20 ` Takashi Yano
2020-02-09 13:42 ` Takashi Yano [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=20200209224223.fd1e411ec7255dd631ba2843@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).