Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!sun!imryrr.Eng.Sun.COM!elric From: elric@imryrr.Eng.Sun.COM (Rick Heli) Newsgroups: comp.windows.x Subject: Re: XAPPLRESDIR, XFILESEARCHPATH, XUSERFILESEARCHPATH (?) Message-ID: <141980@sun.Eng.Sun.COM> Date: 6 Sep 90 23:16:53 GMT References: <803@auto-trol.UUCP> Sender: news@sun.Eng.Sun.COM Distribution: comp Organization: Sun Microsystems, Mt. View, Ca. Lines: 28 In article <803@auto-trol.UUCP> marbru@auto-trol.UUCP (Martin Brunecky) writes: >In article garyo@prometheus.think.com (Gary Oberbrunner) writes: >>Where are these environment variables documented? Are there any others >>like them? What is the recommended policy for using them? >> > > Read the Mit Xt documentation, or the Motif book by G. Young. > > But I suspect you mean something different. Yes, OpenWindows 2.0 > does set those to point into the OpenWindows tree. > I don't like it. I don't think it was intended to be that way. Yeah, in retrospect it would have been better to add a component to XFILESEARCHPATH rather than to set XAPPLRESDIR as the openwin script does now. We'll get this right for the next release. In the meantime, it is possible to get around it by setting XFILESEARCHPATH to something like the following: $HOME/%T/%N%S:$OPENWINHOME/lib/%T/%N%S where in this example the file type (e.g. app-defaults, help, bitmap, etc.) is located inside $HOME. -- Rick Heli Internet: rheli@sun.COM