From: Christian Heller <c.heller@plomlompom.de>
Date: Sat, 6 Apr 2019 22:43:50 +0000 (+0200)
Subject: Fix xterm font setup.
X-Git-Url: https://plomlompom.com/repos/%7B%7B%20web_path%20%7D%7D/static/%7B%7Bdb.prefix%7D%7D/%7B%7Bprefix%7D%7D/templates?a=commitdiff_plain;h=97709a46479eabeec4e3a67f2ed4110ce154c321;p=config

Fix xterm font setup.
---

diff --git a/buster/home_files/eeepc/.Xresources b/buster/home_files/eeepc/.Xresources
index ed6212b..3eb33ae 100644
--- a/buster/home_files/eeepc/.Xresources
+++ b/buster/home_files/eeepc/.Xresources
@@ -2,7 +2,14 @@
 XTerm.termName: xterm-256color
 
 ! font
-XTerm*faceName: -gnu-unifont-*-*-*-*-*-*-*-*-*-*-*
+! actually, "mono" is already the default for faceName (it will
+! pick whatever fc-match mono delivers), but we need to set _some_
+! faceName to trigger XTerm activating TrueType fonts
+! (XTerm*fontRender by itself won't do the trick), and we want
+! TrueType fonts because, well, they scale better, and XTerm lets them
+! fall back on alternatives (hi there ttf-unifont) when a Unicode
+! glyph is not found
+XTerm*faceName: mono
 XTerm*faceSize: 8
 
 ! white on black
@@ -12,4 +19,4 @@ XTerm*reverseVideo: on
 XTerm*visualBell: on
 
 ! proper ALT as META key treatment
-XTerm*eightBitInput:  false
+XTerm*eightBitInput: false