2 ms·
I'm probably one of the only people who liked the .Xresources file. Sure it's a text and you do regexes to specify objects, but I found it easy to customize an
by jandrese 9y ago
I'm probably one of the only people who liked the .Xresources file.
Sure it's a text and you do regexes to specify objects, but I found it easy to customize and because much of it was automatic there would be a ton of the UI variables in it. You want a different color on the background of a particular text box? No problem. You want to change the font used in the app? No problem. You need to customize the contents of a menu? That might be possible! Every application used the same file so you only had to figure it out once.
Granted, you would leave 99% of the variables alone, but it was nice to have the option if you needed it.
Interestingly enough, I still have the file on my box, although I doubt it gets used much anymore. Looking at the file I forgot how you could do a sort of primitive themeing by specifying broad wildcards like "* MenuButton.Background" and "* Toggle.Font"[1]. That's probably a bit dangerous but I can't remember it ever exploding on me spectacularly. Probably because Athena widgets were so damn minimal to begin with.
Oh, man it even still has:
Netscape4*blinkingEnabled: False
Netscape4*myshopping.isEnabled: False
[1] The spaces aren't there in the file, they're just necessary to work around the way HN's markdown does italics.