Just in case: the command > > xrdb -merge .Xresources > > is definitely run when X is called. The resources in .Xresources are > merged with those in /etc/X11. If you issue the same command from a > terminal nothing happens to alter the resources available because > they have already been merged. > > xrdb .Xresources (xrdb -load .Xresources) > > wipes out the resources loaded from /etc/X11 and gives you only what > is in .Xresources. > > Your initial understanding of this led you away from a solution to the > actual problem. Not to worry; everyone does it and everybody learns. :) >
So you mean to say that the resources were already being merged but actually came into effect when I increased their priority or made them more specific by add the class xterm* before the settings! I tried to do this before, I remember very well, but I used Xterm instead of xterm. It was mentioned here. http://unix.stackexchange.com/questions/90608/xterm-not-loading-color-schemes When that never worked I posted on the mailing list. So my question is what do you mean by "Xterm", and then how is "xterm" different? I can guess it has something to do with the class of applications/ instance of applications! -- Regards, Anubhav Yadav Imperial College of Engineering and Research, Pune. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/ca+jf9aen5gqhu4ysat4fg0upz01yxehgcft5y17p6kalou2...@mail.gmail.com
