On Tue, Dec 31, 2013 at 01:58:59PM -0500, Christopher Faylor wrote: >On Tue, Dec 31, 2013 at 10:50:29AM +0100, Bengt Larsson wrote: >>Dawid Ferenczy wrote: >>>The only difference (or one of few) was in the display size. The old laptop >>>has a screen resolution of 1366 x 768 pixels, while the new one has >>>1920 x 1080. And I'm using the whole screen for the terminal window. It's >>>really strange, but if the terminal window height is greater than >>>cca 62 lines, the screen buffer is cleared after quitting the LESS, VIM >>>etc. No matters if Cygwin is executed inside the ConEMu or plain cmd.exe. >>>Making the terminal window smaller solved the problem. Window height >>>of 62 lines seems to be fine for me. Also, with some of greater height >>>values, the LESS/VIM process sometimes crashed. >> >>There does seem to be a problem with the Windows console. I have 64 bit >>Windows 7, and when a console window height*width is bigger than about >>16384, it starts clearing the window after "less". This is running >>"less" from the Windows shell. Not only does it clear the screen, it >>clears it to black, even though I have a different background color. >> >>With mintty and bash it works for me at least up to 383 rows and 1364 >>columns. > >That's because mintty uses entirely Cygwin mechanisms and the console >uses Windows. Windows has a limitation which we didn't know about. >I'll fix this in the next couple of days.
This bug should be fixed in today's snapshot (when it shows up): http://cygwin.com/snapshots/ It will, of course, be in the next Cygwin release but there is no fixed date for when that will be available. -- 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
