X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: font Date: Thu, 1 Dec 2005 09:48:55 -0500 Message-ID: <94BF3137C62D3E4CAED7E97F876585F0D03868@pauex2ku08.agere.com> From: "Williams, Gerald S \(Jerry\)" To: , "Oliver Vecernik" 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id jB1EnaSj002979 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. BTW, you can specify Windows-style fonts for RXVT in your .Xdefaults file. For example, here are the RXVT options in my .Xdefaults file: Rxvt.geometry: 120x50 Rxvt.saveLines: 1000 Rxvt.backspacekey: ^? Rxvt.meta8: true Rxvt.font1: "Lucida Console-10" Rxvt.font2: "Lucida Console-13" Rxvt.font: "Lucida Console-16" Rxvt.font3: "Lucida Console-19" Rxvt.font4: "Lucida Console-22" Rxvt.font5: "Lucida Console-25" Rxvt.font6: "Lucida Console-28" Rxvt.color4: lightblue3 Rxvt.background: rgb:3f/1f/1f Rxvt.foreground: PapayaWhip Rxvt.color12: SteelBlue Rxvt.color15: PapayaWhip Rxvt.scrollBar_right: true Rxvt.scrollstyle: next (I don't know whether the quotes are recommended or not. At least on my system they're not needed, but I've seen other posters use them.) gsw -- 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/