Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3D5299A7.1050505@mscha.org> Date: Thu, 08 Aug 2002 18:17:43 +0200 From: Michael Schaap User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020722 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Console issue References: <3D52160D.7212.F5DF1F@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: at mscha.org by amavisd-milter (http://amavis.org/) On 8-8-2002 15:56, Stephen C. Biggs wrote: > 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. Make sure your TERM environment variable is set appropriately. $ export TERM=cygwin should take care of it. - Michael -- 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/