I am seeing a weird behaviour in xterm (from "native X") when specifying
which "renderfont" (TrueType font) to use from the command line.

This works:

xterm -xrm "xterm.vt100.renderFont: true" \
      -xrm "xterm.vt100.faceSize: 12" \
      -xrm "xterm.vt100.faceName: C64 Pro Mono"

This should be equivalent, and in fact the preferred way (when specifying
the font specifically on the command line), but doesn't work:

xterm -xrm "xterm.vt100.renderFont: true" \
      -xrm "xterm.vt100.faceSize: 12" \
      -fa "C64 Pro Mono"

The exact font probably doesn't matter; this is one which is extremely
easy to spot if it's the correct one or not.

I do have in my ~/.Xresources:

xterm.vt100.faceName:           Lucida Console Semi-Condensed
xterm.vt100.faceSize:           9
XTerm.vt100.renderFont:         false
UXTerm.vt100.renderFont:        true

(but I don't seem to have that font any more)
(I have renderFont: false so that I can set a font in the Xresources but
still start xterm with a bitmap font)

Am I the only one who sees this? I see it with 9.3 and 10.0 RC_1.
Is this something weird with X resource matching?
Something in our import of xterm?
Some bug in upstream? (I tried compiling xterm-388, which is the pkgsrc
version,with plain configure / make, and that showed the same
phenomenon)

-Olaf.
-- 
___ Olaf 'Rhialto' Seibert                            <rhialto/at/falu.nl>
\X/ There is no AI. There is just someone else's work.           --I. Rose

Attachment: signature.asc
Description: PGP signature

Reply via email to