Seems already fixed in win10(16215 Insider).
At 2017-06-09 23:59:20, "Jim Reisert AD1C" <jjreis...@alum.mit.edu> wrote: >On Thu, Jun 8, 2017 at 7:39 PM, yyjdelete wrote: > >> Tested with: >> cygwin: 2.8.0-1 >> bash: 4.4.12-3 >> win: 10 16199(Insider) >> >> When you type `1234567890(Enter)(Enter)(Enter)`, the bash only get `1470`, >> and nothing is shown before the third Enter is press. >> >> It work well after switch to legacy console. >> >> [new_console](https://technet.microsoft.com/library/mt427362.aspx) >> >> Also found here: https://github.com/Alexpux/Cygwin/issues/36 > >I reported a similar problem a few weeks back. It works on the >*released* version of Windows 10 (Creators Update), but broke in one >of the Insider builds. I was hoping to test with Insider build #16215, >but it won't install on my desktop. A lot of people are apparently >having this problem. I did file a Feedback request with Microsoft >about the problem, never heard anything back. > >-- >Jim Reisert AD1C, <jjreis...@alum.mit.edu>, http://www.ad1c.us > >-- >Problem reports: http://cygwin.com/problems.html >FAQ: http://cygwin.com/faq/ >Documentation: http://cygwin.com/docs.html >Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple >
