From: Orgad Shaneh <orgads@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: Typed characters are mis-ordered when CPU usage is high
Date: Thu, 17 Mar 2022 20:40:15 +0200 [thread overview]
Message-ID: <CAGHpTBLe0D9gQaK=4A91w5eravsygpWe001DhcB=hhrcLx6YWA@mail.gmail.com> (raw)
In-Reply-To: <20220312063625.9ca3d42d4e2e941a13fa7909@nifty.ne.jp>
On Fri, Mar 11, 2022 at 11:36 PM Takashi Yano <takashi.yano@nifty.ne.jp> wrote:
> I looked into this problem and found the cause.
> This seems to be due to a bug of fsync(). Cygwin's fsync()
> flushes the console input buffer unlike linux.
>
> I will propose a patch for this issue.
>
> --
> Takashi Yano <takashi.yano@nifty.ne.jp>
Thank you very much. Looks better now.
I'm sorry for nudging, but on msys2 I still get frequent mistypes when
typing fast.
I (still) don't have a consistent reproduction, but if I get it
correctly, it looks like one or more characters I type right when the
prompt appears show up before the buffered characters.
For instance, I run git fetch, and while it is running I type git
status, *sometimes* 1-2 characters "pop" to the left, so I get
something like tgit satus.
I wasn't able to reproduce it with cygwin, but on msys2 (with cygwin
3.3 branch merged in) it happens to me all the time :/
- Orgad
next prev parent reply other threads:[~2022-03-17 18:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 14:39 Orgad Shaneh
2022-02-27 14:53 ` Takashi Yano
2022-03-01 23:12 ` Takashi Yano
2022-03-02 20:13 ` Orgad Shaneh
2022-03-03 0:02 ` Takashi Yano
2022-03-03 3:46 ` Orgad Shaneh
2022-03-10 13:17 ` Orgad Shaneh
2022-03-11 21:36 ` Takashi Yano
2022-03-17 18:40 ` Orgad Shaneh [this message]
2022-03-18 4:23 ` Takashi Yano
2022-03-18 5:22 ` Takashi Yano
2022-03-18 5:57 ` Orgad Shaneh
2022-03-18 6:30 ` Takashi Yano
2022-03-18 6:32 ` Orgad Shaneh
2022-03-18 11:21 ` Orgad Shaneh
2022-03-18 12:15 ` Takashi Yano
2022-03-18 13:04 ` Orgad Shaneh
2022-03-18 13:28 ` Takashi Yano
2022-03-18 6:11 ` n952162
2022-03-02 20:28 ` Kaz Kylheku (Cygwin)
2022-03-03 0:29 ` 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='CAGHpTBLe0D9gQaK=4A91w5eravsygpWe001DhcB=hhrcLx6YWA@mail.gmail.com' \
--to=orgads@gmail.com \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).