Micha Feigin <[EMAIL PROTECTED]> writes:

> I picked up on most of the syntax, but there are a few points, such
> as it appears that using XTerm.  affects all exterms even if they
> were called through a link (x-terminal-emulator for example) while
> xterm.  affects only when called as xterm or whats the difference
> betwin xterm*fonts and xterm.fonts (some apps appear to prefer it
> one way and some the other some take both).

Every widget in the resource tree has a name ('xterm',
'x-terminal-emulator') and a class ('XTerm').  Generally the man page
will list both.  Dots separate items in the tree; a star between items
indicates that zero or more items may be skipped.  So in the
particular case of xterm, that has a widget named vt100 (class VT100),
which lets you specify a font (class Font).  So these are mostly
equivalent:

XTerm.vt100.font: fixed
XTerm.VT100.Font: fixed
XTerm*Font: fixed

(...and all apply to all xterms, regardless of the name they were
started under.)  These make a difference if you have multiple things
with the same class:

xclock.foreground: black
xclock.hands: gray40
! or, would set both of the above:
xclock.Foreground: black

There's a resolution order documented somewhere if you have
conflicting resource settings, which mostly works out to "the most
specific thing takes effect".

-- 
David Maze         [EMAIL PROTECTED]      http://people.debian.org/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
        -- Abra Mitchell


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to