Loading order resolves conflicts between files
If there are two files, then which resource specification from which file
controls the resource in the application? That problem is solved by adhering
to a loading order for files. The following is a list of the standard places, in
order, that an application looks to find resources:
The application default file.
The application default file for the graphical interface is called
HP64_Debug. This file is created at software installation time and placed
in the system application defaults directory.
This environment variable defines an alternative directory path leading to
customized class files. Useful for directing the application to system-wide
RESOURCE_MANAGER property. Some X servers have a resource
property associated with the root window for the server. Resources are
added to the resource property database by using xrdb. (HP VUE is an
example.) The server can use this property to access those resources.
If no RESOURCE_MANAGER property exists, then
$HOME/.Xdefaults is read. The primary and probably best method for
creating or adding to this file is by copying part or all of the app-defaults
file into the .Xdefaults file.
$XENVIRONMENT file. This environment variable defines a file that
contains resource specifications.
If the XENVIRONMENT variable is not set, then
$HOME/.Xdefaults-host is read.
Command line options
Resources can be specified on the command line by using the -xrm
command line option. The application strips these arguments out and
sets these resources before passing the rest of the command line on to the
Remember, load order specifies the precedence for resource overrides. A
resource found later in the load order overrides a resource found earlier in the
load order if the resource specifications match each other.
Chapter 8: X Resources and the Graphical Interface