I'm not sure of the relationship between ~/.Xdefaults and
~/.Xresources and any variant of the two.
The difference is that ~/.Xdefaults is read by libXt-based
programs (such as XTerm) each time one is started, whereas
.Xresources is read by xrdb(1), typically once during user
session initialization (from /etc/X11/Xsession or the like.)
Noel Hunt <noel.hunt@gmail.com> writes:
I'm not sure of the relationship between ~/.Xdefaults and
~/.Xresources and any variant of the two.
The difference is that ~/.Xdefaults is read by libXt-based programs
(such as XTerm) each time one is started, whereas .Xresources is
read by xrdb(1), typically once during user session initialization
(from /etc/X11/Xsession or the like.)
There seems to be some misunderstanding about how xrdb works. It
reads no file by default, the user must supply a file as argument, or
make it available on stdin. Hence, the name of the file is
irrelevant; I think '.Xresources' was simply a convention.
I believe xrdb loads a special resource named 'RESOURCE_MANAGER' into
the X server and clients will read resources from that, rather than
read files. Without this resource present, clients will read from
files (via the X11 libraries), in particular, the older method of
reading from the file '.Xdefaults'.
FTR, I stand by my suggestion to /avoid/ using Go*gle Grou*s in place
of a proper newsreader for participating in Usenet discussions, as it
makes a really poor substitute.
I wasn't aware that ~/.Xdefaults gets ignored when server-side X resources are present, thanks.
That said, libXt applications will still (try to) read
.Xdefaults-${HOSTNAME} -- and, of course, whatever appropriate under XAPPLRESDIR, HOME, or /etc/X11/app-defaults; consider, e. g.:
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 465 |
Nodes: | 16 (2 / 14) |
Uptime: | 39:49:47 |
Calls: | 9,400 |
Files: | 13,569 |
Messages: | 6,098,629 |