X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=D4gwiS0Pp6H8DuPbEcb53tstMYiSHHBiQ8AEhDpN/yKG7DzNjmC3n
	EERl2rjZ/y7gDlHOZWSF6WE1gUB4SzVEsNxet6S+5dEKW664n/wNcElRV5wqTj2Z
	hxyDjH0GqbLdHxJmEUPd2UUZqfLPDHbEpuV4+oJ74yz4lu8yEXVOA4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=PoIH77VuPj2XIaNvO1j8Qq3iiNM=; b=mgebn+LtPpn5n1Pn7hgKlnrizdND
	r6QBbKRMX4Kf6QKEdNKSa2MlIR5pMPMBuvG/1Hc/Op+KVEYOQ8g1O6T1TMB+sXhT
	qHHxcY2c4AtKNqhbuNHcPEF8uzzcORw10Tfr1++TSQd7puRb3x2UJ2Y39uBp9E2Z
	XW6CeySTw6kArME=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+dl2cK/VEpRec8MAQsswW5
Date: Tue, 31 Dec 2013 17:29:04 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Clearing the buffer after quitting LESS, MAN, VIM etc.
Message-ID: <20131231222904.GA5441@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <loom DOT 20131231T025559-913 AT post DOT gmane DOT org> <8545c95dp8ns21seorjf67o4eueglcarsk AT 4ax DOT com> <20131231185859 DOT GA4460 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20131231185859.GA4460@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.20 (2009-06-14)

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