You are not logged in.
So I originally made a lot of URxvt settings, first in .Xdefaults and later converted to .Xresources.
Then I decided to do what I wanted to do using command line parameters instead, so obviously I removed the settings again from .Xresources and didn't think more of it.
Now however, I've just realized that some of the settings still apply, even without command line parameters and I can't figure out why. They are certainly not in .Xdefaults as it does not exists, nor is it in .Xresources.
In short I'm confused and would very much like some help.
Best regards.
Last edited by zacariaz (2012-08-30 17:49:44)
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline
Did you run this after you made the changes?
xrdb -merge ~/.XresourcesIf you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Did you run this after you made the changes?
xrdb -merge ~/.Xresources
I certainly did, even though I didn't think it necessary. And I just ran it again just to be sure, but no difference I'm sorry to say.
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline
Use load instead of merge. Either that or unset those options in the file, then merge, then feel free to clear out the file.
Unsetting is different than just removing the setting. The parameter "merge" should be a hint - it merges the current database with what is in the file provided. If there is nothing in the file, nothing in the database is changed. Load on the otherhand should reload a clean database with only the options in the provided file. If that fails explicitly unsetting, merging, then clearing the file will do it.
Also, you may want to consider keeping your settings in there, but just changing the class name. Then you can launch different versions of your terminals or apps by just passing a name to them rather than passing several parameters.
Last edited by Trilby (2012-08-30 17:27:52)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Use load instead of merge. Either that or unset those options in the file, then merge, then feel free to clear out the file.
Unsetting is different than just removing the setting. The parameter "merge" should be a hint - it merges the current database with what is in the file provided. If there is nothing in the file, nothing in the database is changed. Load on the otherhand should reload a clean database with only the options in the provided file. If that fails explicitly unsetting, merging, then clearing the file will do it.
Also, you may want to consider keeping your settings in there, but just changing the class name. Then you can launch different versions of your terminals or apps by just passing a name to them rather than passing several parameters.
-load didn't do the trick and as for unsetting, I predict some trouble, but I'll try my best and return in a bit.
For now, thanks.
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline
It's official... I'm an idiot.
I had completely forgotten about the changes I made to rc.xml.
Sorry for the confusion and thanks for the help.
I am a philosopher, of sorts, not a troll or an imbecile.
My apologies that this is not always obvious, despite my best efforts.
Offline