Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!mit-eddie!genrad!decvax!decwrl!ucbvax!TOR.NTA.NO!H_Eidnes%vax.runit.unit.uninett From: H_Eidnes%vax.runit.unit.uninett@TOR.NTA.NO (H}vard Eidnes) Newsgroups: comp.windows.x Subject: Re: Xdefaults files Message-ID: <2084:H_Eidnes@vax.runit.unit.uninett> Date: Wed, 22-Apr-87 14:29:20 EST Article-I.D.: vax.2084:H_Eidnes Posted: Wed Apr 22 14:29:20 1987 Date-Received: Fri, 24-Apr-87 05:23:50 EST References: <8704202005.AA23488@vulcan.dec.com> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 21 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}vard Eidnes (or TeXish: H\aa vard Eidnes) Division of Computer Science, Norwegian Institute of Technology