X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6FB3F3986413
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1625742841;
	bh=cPbiPPSPKx3Ct1/p1iIh6LEBQMs4p7EUhXolSHTG16A=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=pDm4E3/HuNrYNjZnSNBWoGOlwBRFKFjF04jrPYeSrgBl++msrvkTdIB0O4wHOsYEs
	 WXg6tiE1pxK6/+tHYBAEkLQ1sOCViphb8EL+oIIaIsUeKEEx5JK6V7ZhhiAhgpE1KG
	 C+HcydlBqqD1J4QcMsZ9wG1wvYYemFRA/qAXx+QY=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A8330385481D
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 168BCY6K002453
X-Nifty-SrcIP: [14.3.237.126]
Date: Thu, 8 Jul 2021 20:12:36 +0900
To: cygwin AT cygwin DOT com
Subject: Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken
Message-Id: <20210708201236.ca1ddf749eb45300f6faad01@nifty.ne.jp>
In-Reply-To: <CAAQS+t8pDsLZtoJEfR+NQjRpUp2M9ZaLkmKbthCXiwvfE4j_Ag@mail.gmail.com>
References: <CAAQS+t-0a0Y=TpgskYe+uCBwNLe4Mdzmi4_ZTjrGqeBYrgdvuw AT mail DOT gmail DOT com>
 <2710589360 DOT 20210707215528 AT yandex DOT ru>
 <CAAQS+t8pDsLZtoJEfR+NQjRpUp2M9ZaLkmKbthCXiwvfE4j_Ag 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=-3.6 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
 SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: <https://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: <https://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>
Cc: =?ISO-2022-JP?B?GyRCJyYnVCdgJ2InYCdTGyhCIBskQicmJ1QnYCdiGyhC?=
 <egor DOT y DOT egorov AT gmail DOT com>
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Thu, 8 Jul 2021 16:35:41 +0600
Егоров Егор via Cygwin <cygwin AT cygwin DOT com> wrote:
> Hello!
> May be bisect result help:
> 
> e_egorov AT 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 AT cygwin DOT 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 DOT yano AT nifty DOT ne DOT 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 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