Bug#858142: xterm: 'xrdb -merge .Xresources' vs 'xrdb .Xresources'
This bug is also triggered if a face size of 12 is used.
After playing around with xrdb(1), I came to suspect there might be
trouble in that program. This is what I did:
Move .Xresources to .Xresources-foo, then log out and in again. This
ensures that your .Xresources file won't load. When xterm is started,
you'll get a much-too-small window and a visible underscore.
Then type "xrdb -merge .Xresources-foo". I got an xterm with all my
settings but now the underscore is invisible -- the buggy state.
Log out and in again. Start an xterm and note that it's back to the
much-too-small default. Now type "xrdb .Xresources-foo" making sure not
to use any flags, particularly "-merge". This will cause xterm to have
the desired settings. Underscores are now visible.
Here's my .Xresources file:
xterm*faceName: DejaVu Sans Mono :antialias=true
xterm*faceSize: 12
XTerm*renderFont: true
XTerm*utf8: 1
xterm*vt100.initialFont: 3
xterm*loginShell: true
xterm*vt100*geometry: 80x24
xterm*saveLines: 2000
xterm*charClass: 33:48,35:48,37:48,43:48,45-47:48,64:48,95:48,126:48
xterm*foreground: rgb:ee/ee/ee
xterm*background: rgb:00/00/00
--
David Griffith
dave@661.org
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
Reply to: