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=RMSXyj9o6gt88p+CgrFt1Koy6Nmtrd5exjqsr1OT9FGYWSeKH6bKu
	Xs8LiBqtBVx8RSOsz7Df12Boqu3HYJ0AZVRmy78CIKPgjouz17RTXDCA+YjbQLP2
	1FOdKMV0eYvO4XbtY+HAXDkxeq8oYASUHZftXhN6zkvs+aGxpQ8FfU=
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=UQhnS1V/PzdvKt8LjImh4rRhk4c=; b=n0XgtJtO6WJIRhrZhdIxqnGyOHJ6
	Rk/R0MYIML+fuv762pejOI+weUxRRLqjl6f6rw3LR+sF3sjB60fzRISmfniw2tsO
	JdTwPe09JMjG2FbAYoVcwQh4rFFSVdI1fZFqukX21QMdZBu+Mr+eJfHmMnks343t
	bT5Natbq98ywtFM=
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.8 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:	U2FsdGVkX18+3h/2H8H+DjufJFzs3/zx
Date:	Sun, 16 Feb 2014 12:21:51 -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:	<20140216172151.GB4830@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20131231185859 DOT GA4460 AT ednor DOT casa DOT cgf DOT cx> <20131231222904 DOT GA5441 AT ednor DOT casa DOT cgf DOT cx> <loom DOT 20140103T011837-791 AT post DOT gmane DOT org> <20140103065626 DOT GB2538 AT ednor DOT casa DOT cgf DOT cx> <loom DOT 20140104T042813-236 AT post DOT gmane DOT org> <CAM9pMnOF4JVzWjSoMKc2bhTd3ApS5BkHW10W+5MFq9LVxPrxrA AT mail DOT gmail DOT com> <20140105234943 DOT GA2524 AT ednor DOT casa DOT cgf DOT cx> <loom DOT 20140129T182024-324 AT post DOT gmane DOT org> <20140129190918 DOT GB2303 AT ednor DOT casa DOT cgf DOT cx> <loom DOT 20140212T140130-348 AT post DOT gmane DOT org>
MIME-Version:	1.0
In-Reply-To:	<loom.20140212T140130-348@post.gmane.org>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Wed, Feb 12, 2014 at 01:33:19PM +0000, Dawid Ferenczy wrote:
>I'm working with CLI having long scrollback buffer. I need to read 
>something a couple of pages back, so I scroll back in the buffer. Then I 
>clear the screen with CTRL + L. Screen is already cleared, but only the 
>visible screen in the middle of scrollback buffer. When content fulfills 
>the whole screen and it starts to scroll, the new output is mixed with 
>previous buffer content. Also scrollback buffer is now messed.
>
>I think, that clearing of the screen with CTRL + L should work as in the 
>Linux terminal (e.g. Gnome Terminal). When I press CTRL + L in the middle 
>of scrollback buffer, it just jumps to the end of scrollback buffer. 

Getting that kind of functionality in the Windows console is tricky but
I think it should be there in the latest snapshot.  I also fixed some
problems with some of the escape sequences that scroll the screen.

There is still one more difference between Cygwin and, e.g., xterm
though.  The scroll buffer is still there when you enter a full screen
session like vim or less.  So you can scroll up to it and really cause
confusion.  It's possible to fix that behavior but it would be really
tricky.  I'm not sure I want to complicate the console handling code
for this one corner case.

The new behavior is in the latest snapshot.

http://cygwin.com/snapshots/

cgf

--
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

- Raw text -