Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 8 Aug 2002 16:33:46 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Console issue Message-ID: <20020808203346.GC14854@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3D52160D DOT 7212 DOT F5DF1F AT localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Thu, Aug 08, 2002 at 12:06:52PM -0700, Karl Zilles wrote: >Stephen C. Biggs wrote: >>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 had this problem when scrolling back to look at long steams of output >from tomcat. Then I'd hit return and instead of returning the view to >the cursor, it would move the cursor up to the location I was viewing >(on top of the output text). > >I think this is a bug/limitation of the windows console and not a cygwin >problem. I changed to rxvt, and in addition to getting rid of that >problem, I get better terminal emulation on some of the systems I ssh to. It is a cygwin problem. It could be fixed in fhandler_console.cc but, so far, in the last five years where this has been a problem, no one has stepped forward to do so. cgf -- 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/