🚀 go-pugleaf

		Xterm, like most X programs, looks for entries in the
		.Xdefaults file for a program named argv[0], not for
		one named "xterm".

	Ummm, welll... That turns out to not be the case. There are
	quite a few "xterms" floating around that actually look for
	"xterm" in .Xdefaults regardless of arg[0]. The main reason
	for that is to avoid having duplication of .Xdefaults entries
	for all of the xterm defaults that are the *same*, and the
	rationale is that they have more in common than they are
	different.

Proposed solution (whenever the uniform approach mentioned does not
work or is not applicable): look at argv[0] first, then at the "generic"
tool name. This should at least solve the problem of having multiple 
occurrances of the same default value in the xterm case.
-------
E-Mail:	<h_eidnes%vax.runit.unit.uninett@nta-vax.arpa>
H}vard Eidnes	(or TeXish: H\aa vard Eidnes)
Division of Computer Science, Norwegian Institute of Technology