On Jun  1 11:22, Ken Brown wrote:
> On 6/1/2016 10:33 AM, Ken Brown wrote:
> > On 6/1/2016 10:28 AM, Corinna Vinschen wrote:
> > > Hi Ken,
> > > 
> > > On Jun  1 09:02, Ken Brown wrote:
> > > > On 6/1/2016 8:51 AM, Ken Brown wrote:
> > > > > On 5/31/2016 5:41 AM, Corinna Vinschen wrote:
> > > > > > Any chance you could bisect Cygwin to help finding the culprit?
> > > > > 
> > > > > The culprit is
> > > > > 
> > > > > commit 252a07b0ad3353abcd0fcd9b1b65ff977acd679e
> > > > > Author: Takashi Yano <takashi.yano@nifty.ne.jp>
> > > > > Date:   Fri Apr 3 13:07:35 2015 +0900
> > > > > 
> > > > >    Cygwin hangs up if several keys are typed during outputting a lot of
> > > > > texts.
> > > > > 
> > > > >        * fhandler_tty.cc (fhandler_pty_slave::read): Change
> > > > > calculation of
> > > > >        "readlen" not to use "bytes_in_pipe" value directly.
> > > > > 
> > > > > 
> > > > > Reverting that commit fixes the problem.
> > > > 
> > > > Unfortunately, all kinds of other things break.  For example, emacs
> > > > exits
> > > > immediately, ls produces no output,....
> > > 
> > > Are you sure?  I just tried it myself and ls as well as emacs work
> > > fine for me.
> > 
> > It works for me now too.  I must have done something wrong the first
> > time I tried.
> 
> And this also fixes the original problem in emacs that started the thread:
> 
>   https://www.cygwin.com/ml/cygwin/2016-05/msg00318.html

I reverted commit 252a07b0ad3353abcd0fcd9b1b65ff977acd679e in git master
for now, unless we find a reason to rework this again.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat