From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-developers@cygwin.com
Subject: Re: [PATCH v6 1/1] Cygwin: pty: add pseudo console support.
Date: Thu, 15 Aug 2019 16:08:00 -0000 [thread overview]
Message-ID: <20190816010759.a119e95e367a4911d46e781b@nifty.ne.jp> (raw)
In-Reply-To: <a623a13e-654f-f06c-a3f9-98daab4fddf2@towo.net>
Hi Thomas,
Thanks for testing.
On Tue, 13 Aug 2019 23:14:49 +0200
Thomas Wolff wrote:
> â¯non-ASCII output fails in non-Unicode mintty
> â¯non-ASCII output fails in non-Unicode mintty
> â¯fails in cmd within non-Unicode mintty (LC_ALL=en_US mintty)
> â¯fails in cmd within non-Unicode mintty (LC_ALL=en_US mintty)
I have worked on these problem, and improved character code conversion.
I will post v7 patch soon in which the problem in non UTF-8 terminal
is fixed.
> The same program, compiled with cygwin gcc, fails in mintty:
> output is skipped (like without the patch)
> â¯input stalls, kill -9 fails.
> Without conpty patch v6, both output and input are skipped.
> Note that winpty properly handles this case.
This problem is hard to be fixed in the current implementation...
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2019-08-15 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 12:10 [PATCH v6 0/1] Pseudo console support in PTY (v6) Takashi Yano
2019-08-12 12:10 ` [PATCH v6 1/1] Cygwin: pty: add pseudo console support Takashi Yano
2019-08-12 13:44 ` Thomas Wolff
2019-08-12 14:57 ` Corinna Vinschen
2019-08-12 15:11 ` Takashi Yano
2019-08-12 15:37 ` Corinna Vinschen
2019-08-12 15:44 ` Takashi Yano
2019-08-12 18:25 ` Corinna Vinschen
2019-08-13 21:14 ` Thomas Wolff
2019-08-15 16:08 ` Takashi Yano [this message]
2019-08-15 18:22 ` Thomas Wolff
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=20190816010759.a119e95e367a4911d46e781b@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-developers@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).