On 2017-05-07 17:24:43 -0400, Thomas Dickey wrote:
> Perhaps you'll see it here:
>
> http://invisible-island.net/xterm/manpage/xterm.html#VT100-Widget-Resources:renderFont
>
> Most of xterm's options work by setting resource values (there are a
> handful of special cases such as "-help", "-version" which do not).
> I can clarify the manual, but there's no reason to change the
> program logic (in this bug, anyway).
The behavior is not what is described in this section. I would agree
if renderFont were "true". But the manual says:
The default is "default".
(and I haven't changed it). For "default":
startup using the normal (bitmap) font, but enable the
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"TrueType Fonts" menu entry to allow runtime switching
to/from TrueType fonts.
If there is no faceName resource set, then runtime
switching to TrueType fonts is disabled. Xterm has a
separate compiled-in value for faceName for the special
case where renderFont is "default". That is normally
"mono".
So, according to the manual, I should get the bitmap font.
Moreover, the text for "-fn font" is not sufficient.
This option specifies the font to be used for displaying normal
text. The corresponding resource name is font. The resource
value default is fixed.
First, it is not mentioned that the font must be a bitmap font (?).
For instance, it does not work with "Monospace". It should also be
clarified when the -fn option is ignored.
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
