delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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 |
From: | "Stephen C. Biggs" <yyyyy50 AT hotpop DOT com> |
To: | cygwin AT cygwin DOT com |
Date: | Thu, 08 Aug 2002 06:56:13 -0700 |
MIME-Version: | 1.0 |
Subject: | Console issue |
Message-ID: | <3D52160D.7212.F5DF1F@localhost> |
Is this a known issue? I have my cygwin shortcut properties modified in the layout to allow for 9999 screen buffer lines. I fire up a console, and hit enter a whole bunch of times so that the scroll bar moves a bit down. Then I go into vi on a big text file and while in vi, tap above the scroll thumb a few times to page up in the console. Then I do :q and when I start hitting enter again, the contents of what was in vi is still present in the screen buffer. This means that I have to hit enter a lot of times to get past it. I hope I explained this understandably. -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |