public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Thomas Dickey <dickey@his.com>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: XWin: Tiny fonts on high resolution display
Date: Sat, 29 Sep 2018 12:49:00 -0000	[thread overview]
Message-ID: <57d99e49-511d-308c-147d-125c30e7f4ee@cornell.edu> (raw)
In-Reply-To: <587877532.53563.1538224490561.JavaMail.zimbra@his.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2768 bytes --]

On 9/29/2018 8:34 AM, Thomas Dickey wrote:
> 
> 
> ----- Original Message -----
> | From: "Ken Brown" <kbrown@cornell.edu>
> | To: "Thomas Dickey" <dickey@his.com>
> | Cc: "cygwin" <cygwin@cygwin.com>
> | Sent: Friday, September 28, 2018 10:25:17 PM
> | Subject: Re: XWin: Tiny fonts on high resolution display
> 
> | On 9/28/2018 8:06 PM, Thomas Dickey wrote:
> |> ----- Original Message -----
> |> | From: "Ken Brown" <kbrown@cornell.edu>
> |> | To: "cygwin" <cygwin@cygwin.com>
> |> | Sent: Friday, September 28, 2018 6:32:25 PM
> |> | Subject: XWin: Tiny fonts on high resolution display
> |>
> |> | A Google search shows that this is a very frequently asked question (e.g.,
> |> | https://sourceware.org/ml/cygwin/2016-07/msg00247.html), but I haven't found a
> |> | good answer, except perhaps to use Gnome or some other desktop environment.  (I
> |> | haven't tried that yet.)
> |> |
> |> | I just got a new laptop with a 3840x2160 display.  When I start the X server via
> |> | startxwin, xterm and emacs open small windows with tiny fonts.  Here are the
> |> | xterm and emacs settings in my .Xresources:
> |>
> |> But none of those are for fonts.  With bitmap fonts, you generally can use 10x20
> |> (12x24 is not so good).  Otherwise, your choice would be a TrueType font (which
> |> generally have poor coverage of Unicode -- a problem since xterm loads only one
> |> font).
> |> If you don't need to read CJKV, that's okay though...
> |>
> |> With TrueType fonts, you can scale it:
> |>
> |> https://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:faceSize
> |
> | Thanks.  The 10x20 font was still too small, but I was able to get a reasonable
> | xterm by adding
> |
> |   XTerm*faceName: Lucida Console
> |   XTerm*faceSize: 24
> |
> | to .Xresources.  The only remaining problem is that the menus are still tiny.  I
> | saw https://invisible-island.net/xterm/xterm.faq.html#tiny_menus, so I changed
> | 'XTerm*geometry:  80x45' to 'XTerm.VT100.geometry:  80x45'.  But that didn't
> | help.  Do you know how I can fix the menu fonts?
> 
> well, you cannot fix those using TrueType fonts, but since those use only ASCII,
> the poor coverage for 12x24 (the largest bitmap font that I recall) would not
> be a problem.
> 
> (I can work out a suitable resource pattern for that, if you need it).

No, I don't need it.  I never use the menus anyway, so maybe I'll just disable 
the toolbar.  But maybe someone else (Eliot?) would find it useful.

Ken
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

  reply	other threads:[~2018-09-29 12:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29  0:07 Thomas Dickey
2018-09-29  2:25 ` Ken Brown
2018-09-29  3:03   ` Eliot Moss
2018-09-29  4:19   ` Brian Inglis
2018-09-29 12:35   ` Thomas Dickey
2018-09-29 12:49     ` Ken Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-09-28 22:32 Ken Brown
2018-09-29  2:21 ` Eliot Moss

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=57d99e49-511d-308c-147d-125c30e7f4ee@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=dickey@his.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).