From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: setup and mintty (was Re: New setup.exe release?)
Date: Thu, 26 May 2011 01:42:00 -0000 [thread overview]
Message-ID: <4DDDAFFF.1020300@cwilson.fastmail.fm> (raw)
In-Reply-To: <BANLkTi=Ox4TzQDX4zwgw0wRS__cZMrz=Kg@mail.gmail.com>
On 5/25/2011 12:52 PM, Andy Koppe wrote:
> On 25 May 2011 16:26, Charles Wilson wrote:
>> On 5/25/2011 1:17 AM, Andy Koppe wrote:
>>> On 25 May 2011 05:32, Charles Wilson wrote:
>>>>> Maybe when I get home I'll test out a few...
>>>>>
>>>>> Consolas
>>>>> Andale Mono
>>>>> Courier New
>>>>> Lucida Console
>>>>> Vera Sans Mono (or DejaVu LGC Sans)
>>>>> Droid Sans Mono
>>>>> Inconsolata
>>>>> ...
>>>>
>>>> FYI:
>>>> http://cygutils.fruitbat.org/mintty-font-test/
>>>
>>> Good work.
>>>
>>> What mintty version is that though? It seems to be missing the
>>> fallback scheme to (rough) ASCII equivalents for the VT100 graphics
>>> characters.
>>
>> mintty-0.9.8-1
>>
>> The difference MAY be that I didn't actually cat xgraphics each time
>> after changing the font. I merely changed the font, while the earlier
>> xgraphics result was viewable in the terminal. If the fallback scheme
>> relies on actually changing the internally-stored character code, rather
>> than changing which glyph is used to draw that character, then my
>> technique would bypass the fallback.
>
> Yep, that explains it.
Ok, I redid the screenshots, but this time I made sure to cat the
xgraphics file again after changig the font. And, you can see the G0/G1
VT100 line drawing modes, for the less-complete fonts, are getting the
ASCII fallbacks. Except for Terminus, for some reason.
I also added the Consolas-W7 snap you sent, and a new entry for
Liberation Mono.
--
Chuck
--
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
next prev parent reply other threads:[~2011-05-26 1:42 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 ` 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 [this message]
2011-05-26 15:54 ` mintty font test Warren Young
2011-05-27 5:26 ` 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=4DDDAFFF.1020300@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--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).