Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3B66D3B4.8030404@ece.gatech.edu>
Date: Tue, 31 Jul 2001 11:50:12 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713
X-Accept-Language: en-us
MIME-Version: 1.0
To: hans DOT deragon AT visa DOT desjardins DOT com
CC: cygwin AT cygwin DOT com
Subject: Re: Scrolling problems with rxvt.
References: <OF18C418C6 DOT B6CB48E3-ON05256A9A DOT 0058B0AC AT pub DOT desjardins DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

hans DOT deragon AT visa DOT desjardins DOT com wrote:


>   http://sources.redhat.com/ml/cygwin/2001-06/msg00652.html -->
>   When scrolling up past 1 screen in the rxvt term, what you see is not
>   what is just preceeding in the file - stuff is lost and what you see is
>   much earlier (older) output.
>   <--


Not exactly.  You see, some programs (like less and vi) actually use a 
secondary display buffer.  If you use the arrow keys, you can tell less 
(or vi) to change what portion of the file they display in that 
one-screenfull-tall buffer.  However, if you use the scroll bar, you 
then see the primary buffer contents.

That is, less/vim will always ONLY control ONE screenful of data.  If 
you scroll OUT of that screenful, then you see .... bash?

This behavior is what allows bash(?) to restore the previous "bash" 
display after you exit vi or less.

Summary: not a bug.

 
>   http://sources.redhat.com/ml/cygwin/2001-06/msg00390.html -->
>   running the latest version of rxvt it appears that, under certain
>   conditions (several hours of use), the scroll bar "fills up" and no
>   longer functions. That is, it looks exactly like it does when the
>   window is created and there is nothing to scroll.
>   <--


I use rxvt exclusively, in both X and native modes.  I've never seen this.

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/