From: "Walter Dnes" <waltdnes@waltdnes.org>
To: Gentoo Users List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Please explain X fonts?
Date: Thu, 26 Mar 2015 22:15:29 -0400 [thread overview]
Message-ID: <20150327021529.GA2159@waltdnes.org> (raw)
I ran into this issue just now setting up X on my ancient netbook that
I've just re-installed on. It's been an ongoing issue of mine that I've
solved with an ugly hack. I'd like to know "the right way" of doing it.
I have a ~/.xinitrc file like so...
#!/bin/bash
[[ -f ~/.Xresources ]] && xrdb -merge ~/.Xresources /usr/bin/xterm -bg black -fg cyan -geometry 50x9+0+0 -fn lucidasanstypewriter-12 &
/usr/bin/xterm -bg black -fg cyan -geometry +0+0 -fn lucidasanstypewriter-12 &
exec /usr/bin/icewm > ~/.icewm.log 2>&1
Some time ago, somebody decided to deprecate iso8859-1 fonts. And
when I run startx, the text console comes up with
========================================================================
/usr/bin/xterm: cannot load font 'lucidasanstypewriter'
/usr/bin/xterm: cannot load font 'lucidasanstypewriter'
Warning: Cannot convert string "lucidasanstypewriter" to type FontStruct
Warning: Unable to load any usable ISO8859 font
Warning: Unable to load any usable ISO8859 font
Error: Aborting: no font found
Warning: Cannot convert string "lucidasanstypewriter" to type FontStruct
Warning: Unable to load any usable ISO8859 font
Warning: Unable to load any usable ISO8859 font
Error: Aborting: no font found
========================================================================
xterms come up with some dinky little font. It's bad enough on a 24
in 1920x1080 monitor. On an 11" 1366x768 netbook, it's unreadable.
When I do a control-right-click on an xterm to manipulate fonts, the
xterm crashes.
One of the nice things about having multiple machines, is that I still
had another machine with the old fonts. For a few years, I've preserved
a copy of /usr/share/fonts from that machine as fonts_do_not_delete. So
each time fonts are "updated" on my machines, I rename /usr/share/fonts
to /usr/share/fonts.borken and copy the fonts_do_not_delete directory as
/usr/share/fonts.
OK, so whats supposed to be "the right way" to get working xterms with
lucidasanstypewriter-12?
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next reply other threads:[~2015-03-27 2:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 2:15 Walter Dnes [this message]
2015-03-27 3:38 ` [gentoo-user] Please explain X fonts? Matti Nykyri
2015-03-27 22:43 ` [gentoo-user] " walt
2015-03-29 9:23 ` lee
2015-03-29 20:27 ` Urs Schütz
2015-04-02 0:03 ` lee
2015-04-02 20:48 ` Urs Schütz
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=20150327021529.GA2159@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.org \
/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