On Mon, Apr 21, 2025 at 11:26:48AM -0700, googly.negotiator...@aceecat.org wrote: > So they have to be on different machines in the case of using X remotely: > .Xresources on the server, .Xdefaults on the client.
Eh... I didn't really want to dive too deep into the X init process, since it's esoteric/complex, historically sometimes annoyingly dependent on the idiosyncracies of your vendor and your point in time. It's far less common these days that people run X remotely, mostly obviating the distinction between client and server; and what I suggested will work for probably 99.99% of users, even if they do, largely regardless of what antiquated platform they may be stuck on (so long as it's not TOO old or idiosyncratic), so it's really beyond the scope here. But since you raised it, what you said is imprecise: .Xresources is really just a convention--most modern vendors will indeed load it on the server if it exists. However, you can load the resource manager (a property of the server's root window), via xrdb (client), using whatever file you like (including .Xdefaults, etc.) on the client side. The overwhelming majority of users should not care one iota about this and just do something like what I suggested. =8^) -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
