Corbin Bird <corbinb...@charter.net> writes: [...]
Harry wrote: [...] >> googling for hours on this I find xterm can understand a different >> switch `xterm -fa bla-bla' >> >> However, xterm as installed from portage does not understand that >> switch at all. >> >> Some of the googling mentioned that xterm has to have that ability >> compiled in, so I wondered if our xterm is compiled for that option? A very feeble light almost came on above... [...] Harry Putnam <rea...@newsguy.com> writes: > Corbin Bird <corbinb...@charter.net> writes: > > [...] > >> Please clarify ... >> ... if this is a console only boot ( in vm ), >> ... if this is a GUI Desktop ( in vm ), >> and/or specific xterm ( i.e "x11-terms/xterm" ). Harry responds: > This is a full X host running lxde for desktop > The xterm I speak of is the real McCoy .. the one Thomas Dickey has > maintained since mid to late 90s. > > In this case: x11-terms/xterm version 327 But I just noticed when > pretend emerge just now to see what the use flags were... I see it > defaults to -truetype use flag... which may be significant. > > I'm re-emerging with USE=truetype might make some difference. > > But still would not explain the fonts that are not true type failing > to load. > > Do you know if some EXTRA_ECONF or something is needed to make xterm > recognize its -fa switch? > > I've seen in several places that -fa font-name is used instead of -fn > font-name Hitting all around it ... finally I noticed that xterm compiles with Use flag `-truetype' That feeble light finally took on some strength, I set [...] package.use/xterm With contents: `x11-terms/xterm truetype' re-emerged xterm..... And now I'm happily loading fonts with the -fa switch. xterm -fa Inconsolata-Regular.ttf [...] and away it goes .. and a fine looking font it is too.
