public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Егоров Егор" <egor.y.egorov@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin-3.2.0 + windows 10 - russian cyrilic input is broken
Date: Thu, 8 Jul 2021 16:35:41 +0600	[thread overview]
Message-ID: <CAAQS+t8pDsLZtoJEfR+NQjRpUp2M9ZaLkmKbthCXiwvfE4j_Ag@mail.gmail.com> (raw)
In-Reply-To: <2710589360.20210707215528@yandex.ru>

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.

    - Currently, Ctrl-Z, Ctrl-\ and SIGWINCH does not work in console
      if the process does not call read() or select(). This is because
      these are processed in process_input_message() which is called
      from read() or select(). This is a long standing issue of console.
      Addresses:
        https://cygwin.com/pipermail/cygwin/2020-May/244898.html
        https://cygwin.com/pipermail/cygwin/2021-February/247779.html

      With this patch, new thread which handles only input signals is
      introduced so that Crtl-Z, etc. work without calling read() or
      select(). Ctrl-S and Ctrl-Q are also handled in this thread.

 winsup/cygwin/exceptions.cc       |   1 +
 winsup/cygwin/fhandler.h          |   5 +-
 winsup/cygwin/fhandler_console.cc | 177
+++++++++++++++++++++++++++++++++++++-
 3 files changed, 181 insertions(+), 2 deletions(-)

чт, 8 июл. 2021 г. в 01:05, Andrey Repin <anrdaemon@yandex.ru>:

> Greetings, Егоров Егор!
>
> > I have a similar problem too.
>
> Unfortunately, "me too" is not a useful issue report.
>
> > After upgrading to cygwin-3.2.0 the input of Cyrillic characters in the
> > bash console is broken. Can we expect a fix for the problem in the next
> > nightly builds?
>
> Please follow issue reporting guide:
>
> Problem reports:      https://cygwin.com/problems.html
>
> See also:
>
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
>
>
> --
> With best regards,
> Andrey Repin
> Wednesday, July 7, 2021 21:52:50
>
> Sorry for my terrible english...

  reply	other threads:[~2021-07-08 10:35 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   ` Егоров Егор [this message]
2021-07-08 11:12     ` Takashi Yano
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=CAAQS+t8pDsLZtoJEfR+NQjRpUp2M9ZaLkmKbthCXiwvfE4j_Ag@mail.gmail.com \
    --to=egor.y.egorov@gmail.com \
    --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).