public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: mintty font test
Date: Thu, 26 May 2011 15:54:00 -0000	[thread overview]
Message-ID: <4DDE7789.2030901@etr-usa.com> (raw)
In-Reply-To: <4DDDAFFF.1020300@cwilson.fastmail.fm>

On 5/25/2011 7:42 PM, Charles Wilson wrote:
>>>>> FYI:
>>>>> http://cygutils.fruitbat.org/mintty-font-test/
>
> Ok, I redid the screenshots, but this time I made sure to cat the
> xgraphics file again after changig the font.

This is really valuable, Chuck!  I'd already independently settled on 
Deja Vu and Lucida Console already based on ad hoc testing, but these 
test results give me a objective foundation for that opinion.

(Why Lucida Console given its deficiencies compared to Deja Vu?  It's 
more vertically compact, allowing more lines in a window for a given 
point size, and I don't seem to have any programs here that need the 
missing glyphs.)

If random list members can nominate others for gold stars, I so do. :)

It might be good if this xgraphics file you have were distributed with 
mintty in the doc directory, so others can repeat the test on their 
system with other fonts.

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

  reply	other threads:[~2011-05-26 15:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTinMD5ys8KMYdcTpMPXYc9uVYdhquw@mail.gmail.com>
     [not found] ` <20110523115058.GJ3051@calimero.vinschen.de>
     [not found]   ` <4DDA7E64.3060202@cwilson.fastmail.fm>
     [not found]     ` <20110523160437.GN3051@calimero.vinschen.de>
     [not found]       ` <BANLkTiks+fRTqkEJx_2ic-qZ33p5s936Vg@mail.gmail.com>
     [not found]         ` <4DDACA2C.6080201@cwilson.fastmail.fm>
     [not found]           ` <4DDC867B.6040000@cwilson.fastmail.fm>
2011-05-25  5:17             ` setup and mintty (was Re: New setup.exe release?) Andy Koppe
2011-05-25 15:27               ` Charles Wilson
2011-05-25 15:54                 ` KHMan
2011-05-25 16:14                   ` Ryan Johnson
2011-05-25 16:20                     ` KHMan
2011-05-25 16:55                     ` Andy Koppe
2011-05-25 18:05                       ` Ryan Johnson
2011-05-25 20:49                         ` Thomas Wolff
2011-05-26  6:05                           ` Corinna Vinschen
2011-05-25 16:53                 ` Andy Koppe
2011-05-26  1:42                   ` Charles Wilson
2011-05-26 15:54                     ` Warren Young [this message]
2011-05-27  5:26                       ` mintty font test Andy Koppe
2011-05-27  5:30                         ` Andy Koppe
2011-05-31 15:17                           ` Charles Wilson
2011-05-31 18:19                             ` Thomas Wolff
2011-06-01 20:07                               ` Thomas Wolff
2011-06-01  5:27                             ` Andy Koppe
2011-06-01 15:45                               ` Charles Wilson
2011-06-01 18:15                                 ` Andy Koppe
2011-05-25 21:41               ` setup and mintty (was Re: New setup.exe release?) Charles Wilson

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=4DDE7789.2030901@etr-usa.com \
    --to=warren@etr-usa.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).