From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: John Hood <cgull@glup.org>
Subject: Re: Vim responds too slow on the latest snapshot of cygwin1.dll
Date: Mon, 06 Jun 2016 08:43:00 -0000 [thread overview]
Message-ID: <20160606084328.GD14744@calimero.vinschen.de> (raw)
In-Reply-To: <20160606003303.ecd888597a40bd1081308452@nifty.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
On Jun 6 00:33, Takashi Yano wrote:
> Hello, everyone.
>
> I tested the latest snapshot of cygwin1.dll, and
> noticed that vim editor respond too slow on it.
>
> When I open some file with vim, the text appears
> after a few seconds. ^F and ^B keys also update
> the screen very slowly.
This is what is being discussed in the thread starting at
https://cygwin.com/ml/cygwin/2016-05/msg00327.html
Just as John I can't reproduce this. What OS version do you run this
on, and is it 32, 32 under WOW64, or 64 bit?
> I tried to bisect the problem, and found that this
> problem occurs after :
>
> commit e5665d8c930485d5ac6d8913573e27b9e5043d92
> Author: John Hood <cgull@glup.org>
> Date: Wed May 18 19:14:17 2016 -0400
>
> Improve and simplify select().
>
> * select.h: Eliminate redundant select_stuff::select_loop state.
> * select.cc (select): Eliminate redundant
> select_stuff::select_loop state. Eliminate redundant code for
> zero timeout. Do not return early on early timer return.
> (select_stuff::wait): Eliminate redundant
> select_stuff::select_loop state.
>
> I hope this problem will be fixed before release.
Me, too, especially since we're going to have to release 2.5.2 this week.
If we don't have a solution I'll revert this patch for 2.5.2 and we can
reapply and improve it for 2.6 then. Of course it would be nicer to
have a fix :}
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-06 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 15:33 Takashi Yano
2016-06-06 8:43 ` Corinna Vinschen [this message]
2016-06-06 11:06 ` Takashi Yano
2016-06-06 13:50 ` Chris Sutcliffe
2016-06-06 14:52 ` Corinna Vinschen
2016-06-06 16:15 ` Chris Sutcliffe
2016-06-07 12:38 ` Takashi Yano
2016-06-07 13:12 ` Corinna Vinschen
2016-06-08 1:21 ` John Hood
2016-06-08 9:00 ` Corinna Vinschen
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=20160606084328.GD14744@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cgull@glup.org \
--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).