[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#263877: Various display artifacts in uxterm



On Fri, Aug 06, 2004 at 11:01:00AM -0700, Matt Zimmerman wrote:
> On Fri, Aug 06, 2004 at 01:17:32PM -0400, Thomas Dickey wrote:
> 
> > On Fri, Aug 06, 2004 at 09:35:57AM -0700, Matt Zimmerman wrote:
> > > I have the standard xfonts-* packages installed, and UXTerm*font: 9x15.
> > 
> > "UXTerm*font: 9x15" could be a different problem.  xterm uses two sets of
> > fonts.  An "*" (asterisk) will cause the iso10646 fonts to be ignored since
> > they're given by a path such as
> > 
> > 	uxterm.vt100.utf8fonts.font
> > 
> > which would conflict with (what you intend the 9x15 to apply to):
> > 
> > 	uxterm.vt100.font
> 
> This was copied from my old xterm resources.  I just tried changing it to
> "uxterm.vt100.font", but that seems to cause it to revert to the default
> font.

sorry (I was fumbling around a display bug in PuTTY, should have read
my reply more closely).  uxterm sets the "UXTerm" class for xterm, which
would mean you'd need 

	UXTerm.vt100.font

instead.  The application name would still be "xterm" - though I have noticed
at least one distributor renaming xterm to something like "xterm.real" -
and referencing it via a symbolic link, breaking all the resource settings.

A quick check of the above seems to work for me (ymmv).

More generally, I configure xterm with the toolbar, which adds a level.
But
	UXTerm*vt100.font

is still more limited than

	UXTerm*vt100*font
or
	UXTerm*font

-- 
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Attachment: pgpDohnszUhQ1.pgp
Description: PGP signature


Reply to: