Why doesn't .Xdefaults work

[Collins Richey]

On Thu, 27 Mar 2003 17:02:41 -0800
Bill Campbell <bill at celestial.com> wrote:

> On Thu, Mar 27, 2003 at 05:21:07PM -0700, Collins Richey wrote:
> >On Sun, 23 Mar 2003 03:13:48 +0100
> >Norbert Augenstein <norbert at augenstein.net> wrote:
> >
> >> On Sat, Mar 22, 2003 at 03:30:32PM -0700, Collins Richey wrote:
> >> > I'm not sure how long this has been going on, but it's got me
> >> > buffaloed.
> >> > 
> >> > I have the following in ~/.Xdefaults, and this used to work:
> >> > 
> >> > # this is .Xdefaults
> >> > aterm*background '#ffffe0'
> > ... 
> >> > aterm*savedLines 500
> >> > 
> >
> >> suggest using colons
> >> 
> >
> >Previous hint (Llama) was check ~/.xsession-errors, but absolutely
> >nothing in that file.
> >
> >What do you mean by "use colons"?
> 
> If you're using KDE, make sure that there isn't an app-defaults file
> for the aterm under /opt/kde*.  I run into this with xterms in that my
> $HOME/XTerm file is ignored unless I comment out everything in the
> /opt/kde3/share/apps/kdisplay/app-defaults/XTerm.ad file. 
> Incidentally, the comment character in these files is ``!'' not the
> usual ``#''.
> 
> KDE, in its infinite wisdom, seems to read its own app-defaults files
> _AFTER_ anything in the user's home directory (SCO OpenServer does
> much the same way, using proprietary color names as well which really
> screws things in Linux xterms).
> 

Thanks, that's handy to know.  But I get the same behavior with xfce,
xxbox, windowmaker, etc.

--
Collins