From: Thomas Dickey <dickey@his.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: cygwin <cygwin@cygwin.com>
Subject: Re: XWin: Tiny fonts on high resolution display
Date: Sat, 29 Sep 2018 00:07:00 -0000 [thread overview]
Message-ID: <20180929000647.GA2323@prl-debian8-64.jexium-island.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
----- 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
|
| emacs.geometry: 80x34+340+40
| XTerm*geometry: 80x45
| XTerm*VT100*colorBDMode: on
| XTerm*VT100*colorBD: blue
| XTerm.VT100*colorULMode: on
| XTerm.VT100*underLine: off
| XTerm*VT100*colorUL: magenta
| XTerm*scrollBar: true
| XTerm*rightScrollBar: true
| XTerm*saveLines: 10000
| XTerm*metaSendsEscape: true
|
| I'm attaching my cygcheck output and XWin log.
|
| Thanks in advance for any suggestions.
|
| Ken
--
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2018-09-29 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 0:07 Thomas Dickey [this message]
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
-- 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=20180929000647.GA2323@prl-debian8-64.jexium-island.net \
--to=dickey@his.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).