X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <BLU113-W21177A15E434E33E07115BEA80@phx.gbl>
References: <BLU113-W522658FEAE3057BCCA6BEDBEA80@phx.gbl> 	 <416096c60903011234y3434e47wcfc86421e35b5dcb@mail.gmail.com> 	 <BLU113-W21177A15E434E33E07115BEA80@phx.gbl>
Date: Sun, 1 Mar 2009 16:35:31 -0500
Message-ID: <17393e3e0903011335s7b7ce1d7lb94ddce87e9a653d@mail.gmail.com>
Subject: Re: console scroll speed on Win XP
From: Matt Wozniski <godlygeek@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Sun, Mar 1, 2009 at 3:54 PM, Mike Marchywka wrote:
>>
>>> Is there some option to turn off to make this reasonable or has anyone
>>> else seen this problem? I set display options to maximize performance
>>> and there don't seem to be any options available for the cygwin window
>>> that would help.
>>
>> Yep, the Windows console is slow alright, and I don't know of any way
>> to speed it up. What I can recommend are the alternative terminal
>> emulators available in Cygwin: xterm, rxvt, and the recently added
>> mintty (by yours truly), all of which scroll a lot faster than the
>> console.
>>
>> (Please note that all three share one drawback though: native Windows
>> console programs might not work correctly in them, particularly
>> input.)
>
> What is wrong with the native apps ? I use them in some scripts
> but usually not interactively. I don't normally care about text
> formatting if output is just a bit different.

IO buffering won't work the way they expect when they don't have a
real console.  So, you wind up with weird conditions like the program
waiting for input after printing out a prompt - but the app didn't
call fflush(), so the prompt hasn't actually been displayed, but it's
still waiting for you to answer the question.  Using them in a
scripted way should work fine, it's just interactive usage that you
would expect to be broken.

~Matt

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

