From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: "Егоров Егор" <egor.y.egorov@gmail.com>
Subject: Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken
Date: Thu, 8 Jul 2021 20:12:36 +0900 [thread overview]
Message-ID: <20210708201236.ca1ddf749eb45300f6faad01@nifty.ne.jp> (raw)
In-Reply-To: <CAAQS+t8pDsLZtoJEfR+NQjRpUp2M9ZaLkmKbthCXiwvfE4j_Ag@mail.gmail.com>
On Thu, 8 Jul 2021 16:35:41 +0600
Егоров Егор via Cygwin <cygwin@cygwin.com> wrote:
> Hello!
> May be bisect result help:
>
> e_egorov@inp-w-egorov-e /tmp/newlib-cygwin
> $ git bisect bad
> ff4440fcf7687d9af05f4c2fcb163fca5b2167f9 is the first bad commit
> commit ff4440fcf7687d9af05f4c2fcb163fca5b2167f9
> Author: Takashi Yano via Cygwin-patches <cygwin-patches@cygwin.com>
> Date: Tue Feb 16 20:37:05 2021 +0900
>
> Cygwin: console: Introduce new thread which handles input signal.
Does your issue also happen after the following commit?
commit 98e3aeb1f521151f5b18fc2af9a8fecf11a98e76
Author: Takashi Yano <takashi.yano@nifty.ne.jp>
Date: Thu Jun 24 12:40:58 2021 +0900
Cygwin: console: Fix garbled input for non-ASCII chars.
- After the commit ff4440fc, non-ASCII input may sometimes be garbled.
This patch fixes the issue.
Addresses: https://cygwin.com/pipermail/cygwin/2021-June/248775.html
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-07-08 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 10:20 Егоров Егор
2021-07-07 18:55 ` Andrey Repin
2021-07-08 10:35 ` Егоров Егор
2021-07-08 11:12 ` Takashi Yano [this message]
2021-07-08 11:20 ` Takashi Yano
2021-07-08 11:53 ` Егоров Егор
-- strict thread matches above, loose matches on Subject: below --
2021-06-22 13:34 Eugene Klimov
2021-06-23 3:09 ` Takashi Yano
2021-06-23 6:07 ` Eugene Klimov
2021-06-23 8:41 ` Takashi Yano
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=20210708201236.ca1ddf749eb45300f6faad01@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=egor.y.egorov@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).