lusgr@vax1.cc.lehigh.edu (Steve Roseman) (03/13/91)
Has anyone else noticed that in X-Windows after updating to 3003, .Xdefaults seem to stop being used after a while? Things work for a few hours, I run normal programs, but then I bring up emacs (for which I have a line 'emacs*Font : Rom14') and it's back to default font. In addition, every other program's .Xdefaults seem to be ignored. Killing X (Ctrl/Alt/Bksp) and restarting restores things. Is this common and to be reported, or am I doing something strange? Steve ------------------------------------------------------------------------- Steve Roseman Lehigh University Computing Center LUSGR@VAX1.CC.Lehigh.EDU
ejk@ux2.cso.uiuc.edu (Ed Kubaitis - CSO ) (03/14/91)
>Has anyone else noticed that in X-Windows after updating to 3003, .Xdefaults >seem to stop being used after a while? Things work for a few hours, ... Perhaps until you happen to use InfoExplorer? If so, here's the story: Info's front-end shellscript does an 'xrdb' which wipes out your resource definitions for all subsequently invoked clients. Circumvention is to comment out the 'xrdb $KEYFILE' in /usr/bin/info. This problem has been reported as APAR IX16234 which suggests editing the script to change xrdb to xmodmap, apparently what was intended. Info also alters the server font paths which creates problems for some non-IBM servers such as NCD & HP (APAR IX16886). IMHO the real problem is clients have no business tampering with font paths, key definitions, resource database, or other server items. Only users or session managers acting on the user's behalf should modify them. At the very least, Info's tampering should be clearly documented and an option provided to bypass it. (Note: I really *like* InfoExplorer. I just find it's behavior arrogant in this regard.) ---------------------------------- Ed Kubaitis (ejk@uxh.cso.uiuc.edu) Computing Services Office - University of Illinois, Urbana
prener@arnor.UUCP (Dan Prener) (03/15/91)
If your .Xdefaults appears to stop being used after a while, it is
most likely that some program has invoked xrdb, which caches the
information in memory, rather than reading it from the .Xdefaults
file whenever it is needed. Look at the xrdb command, particularly
the -merge, -query, -load, and -remove options.
--
Dan Prener (prener @ ibm.com)