From: Paul McFerrin <pmcferrin@columbus.rr.com>
To: cygwin@cygwin.com
Subject: Re: MinTTY "vs" rxvt (was Re: MinTTY 0.3.3)
Date: Mon, 12 Jan 2009 05:14:00 -0000 [thread overview]
Message-ID: <496AC05C.9010403@columbus.rr.com> (raw)
In-Reply-To: <496A54F6.7020107@cwilson.fastmail.fm>
On Sun, Jan 11, 2009 at 03:22:14PM -0500, Charles Wilson wrote:
>Christopher Faylor wrote:
>
>Well, it's my main terminal. I tried MinTTY and I'm not sure yet whether
>it will supplant rxvt for my personal use, but it shows promise.
>
I've been using rxvt for years as my main terminal and just tried using
minTTY and really prefer not to use it. You see I'm and old man with
poor eye sight. The visual attributes of minTTY aren't the same that I
use with rxvt. The Lucida Console (white foreground on black) has less
contrast as the same font on rxvt. If I make it bold, it approaches
nearly the same brightness as rxvt but a little more blurry. These
featurea don't go with poor vision.
I made the mistake of updating rxvt before and I learned no more
updates, please. Maybe it will help someone what options I use to make
my statements more clearer:
rxvt --backspacekey ^H -sbt 15 -fg white -bg black -geometry +75+80 -sr
-title "TTY$tty$label" -tn ansi -sl 3000 -fn 'Lucida Console-12' -e ksh &
My 2 cents worth, no more.
-Paul
--
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/
next prev parent reply other threads:[~2009-01-12 4:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 4:56 pedantic/misled/confused/passive-aggressive " Christopher Faylor
2009-01-11 9:17 ` Yaakov (Cygwin/X)
2009-01-11 20:53 ` MinTTY "vs" rxvt " Charles Wilson
2009-01-11 22:18 ` Andy Koppe
2009-01-11 23:33 ` Charles Wilson
2009-01-12 0:37 ` Andrew DeFaria
2009-01-12 0:45 ` Christopher Faylor
2009-01-12 0:42 ` Christopher Faylor
2009-01-12 5:14 ` Paul McFerrin [this message]
2009-01-12 12:35 ` Andy Koppe
2009-01-12 16:34 ` cgf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=496AC05C.9010403@columbus.rr.com \
--to=pmcferrin@columbus.rr.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).