X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: "Cary Jamison" Subject: Re: font Date: Thu, 1 Dec 2005 13:48:38 -0700 Lines: 24 Message-ID: References: <94BF3137C62D3E4CAED7E97F876585F0D03868 AT pauex2ku08 DOT agere DOT com> X-IsSubscribed: yes 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 In news:94BF3137C62D3E4CAED7E97F876585F0D03868 AT pauex2ku08 DOT agere DOT com, Williams, Gerald S (Jerry) typed: > Chris Taylor wrote: >> Yes. Don't use the cmd-based cygwin interface. >> Use rxvt. > > Agreed. However, expect the occasional surprise when > running non-Cygwin console binaries since they won't > recognize that they are running on a terminal. I use > a Tcl-based debugger at work, and when running it in > Win32 console mode under RXVT, I don't get a prompt. > > If that's not an issue for you, go ahead and don't > look back. I'm always surprised at how many people recommened using rxvt. I use it once in a while, but there's just too many things I do don't work right unless I'm using the regular Win32 console. Output is delayed until the process exits, input is ignored, etc., etc. Cary -- 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/