This is the mail archive of the
mailing list for the Cygwin project.
Re: setup and mintty (was Re: New setup.exe release?)
- From: Andy Koppe <andy dot koppe at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 25 May 2011 17:52:34 +0100
- Subject: Re: setup and mintty (was Re: New setup.exe release?)
- References: <BANLkTinMD5ys8KMYdcTpMPXYc9uVYdhquw@mail.gmail.com> <20110523115058.GJ3051@calimero.vinschen.de> <4DDA7E64.email@example.com> <20110523160437.GN3051@calimero.vinschen.de> <BANLkTiks+fRTqkEJx_2ic-qZ33p5s936Vg@mail.gmail.com> <4DDACA2C.firstname.lastname@example.org> <4DDC867B.email@example.com> <BANLkTimyLFM8+QpwXKHKECmD-9V8x=i5yQ@mail.gmail.com> <4DDD1FAF.firstname.lastname@example.org>
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...
>>>> Andale Mono
>>>> Courier New
>>>> Lucida Console
>>>> Vera Sans Mono (or DejaVu LGC Sans)
>>>> Droid Sans Mono
>> Good work.
>> What mintty version is that though? It seems to be missing the
>> fallback scheme to (rough) ASCII equivalents for the VT100 graphics
> 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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple