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:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=CKJyCxYdkgH4tkEv65WGlBPbO2c0H2Oft5yPZgrQZ3qeBTEu3oCFF
	VPHdhZ1siSvaJtNdpL1vlshqS39AMye45/t5oASyU0l52VjUhrVp4S6tdK1vydGn
	/qQL/8ICPF064lSpoD0RZVAelMLH6g6HMmwtpOgDSf+IVtPBgc+VX8=
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:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding; s=default;
	bh=Vu1PpohF3jYM+j2FsOuVF73q+co=; b=HbTU/O0U+7cahc9UMMUdJ/zAkPJA
	gxw5qTVAOL0slssmCFIBri7Q/3+N9MElSqbpuBewXGnsRzSADIgRAgWtbP0dpwcv
	3r8KglOuc5Zk9z6ZkWHja8apX4Wma2wF3Jx7Y+38tLfCnE4zFKhyZDzKQYVDJzVO
	Np6YvSeEo18TFmc=
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=2.9 required=5.0 tests=AWL,BAYES_20,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,T_FRT_BELOW2 autolearn=no version=3.3.2
X-HELO:	plane.gmane.org
To:	cygwin AT cygwin DOT com
From:	Dawid Ferenczy <ferenczy AT volny DOT cz>
Subject:	Re: Clearing the buffer after quitting LESS, MAN, VIM etc.
Date:	Mon, 24 Feb 2014 17:35:21 +0000 (UTC)
Lines:	64
Message-ID:	<loom.20140224T170219-750@post.gmane.org>
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> <20140216172151 DOT GB4830 AT ednor DOT casa DOT cgf DOT cx>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes

Christopher Faylor <cgf-use-the-mailinglist-please <at> cygwin.com> writes:

> 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



Hi Christopher,

Thank you very much for your interest. But I have to say, it's now worse 
than it was before. I'm using the latest snapshot (2014-02-24).

My findings:

1. Clear screen (CTRL + L) now works better, it simply scrolls to the end 
of the scrollback buffer and appends to it. But the screen isn't cleared, 
what should be the main purpose of the "clear screen" :) After clearing of 
screen, current prompt is on the most bottom line of screen with scrollback 
buffer above. I think that it's should be on the first line of screen and 
the screen bellow should be empty. So add of scroll screen_height lines 
down should be enough to resolve this.

2. Scrollback buffer seems to be fine until I use LESS/VIM etc. 
(alternative screen). Than it's messed. Alternative screen shouldn't 
influence the scrollback buffer, I think.

3. It's incompatible with screen (screen manager). Status line of screen is 
overwritten with screen content and when screen content reaches the most 
bottom line of screen, it doesn't scroll, so any additional content is 
hidden.

- - - - - - - - - -

I really don't know much about how that command line related things works 
in Linux, but could it be possible that you work with screen and scrollback 
buffer wrong way? I mean, maybe there are some rules, how to work with 
screen content and buffer, so it would work everywhere (e.g. in the screen 
manager) rather that trying to fix bugs, write workarounds and hacks.

I wonder that nobody else have similar issues, because this is absolutely 
essential, when you work with terminal, I think. I had none of these 
problems, when I was using smaller screen size. Everything started with my 
new laptop with HD display, because I used to have terminal window in 
fullscreen mode.

Thank you for your time and have a nice day.

-- 
 Dawid Ferenczy
 http://ferenczy.cz


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