-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Sep 23, 2016 at 11:31:20AM +0200, to...@tuxteam.de wrote:
[...] > > It makes a big difference for remote applications, since they will see the > > .Xresources from the server but the .Xdefaults from the client. Forgot to say that typically, .Xdefaults overrides .Xresources, so if you want to take advantage of .Xresources, you better avoid .Xdefaults. But in the widespread one-machine-does-all approach it makes little difference. You'll notice it in a situation like this: imagine a Raspi back there in the closet, with a lo-res display (say, 320x240). You'll want pretty small fonts on that, to fit anything on screen. Now you ssh -X into that from your workstation (1600x1200). The fonts used in the Raspi will be unreadable. The graphical app running on the Raspi should "honour" your workstation's font choice, otherwise you'd need a magnification glass. How? Well, the X server on your workstation is the one doing the display work anyway, and has its own set of .Xresources. Had you set an .Xdefaults on the Raspi, the X library would override that -- most likely not what you want (but if you choose wisely what to set, you might put that to good use, perhaps coluring the windows differently to give you a hint of where the app is running, I don't know). regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlfk+NcACgkQBcgs9XrR2kbWeACfZLV80sFo5Bp8BzblWizm/01Q NGYAniTbQkeNf9QjxKyWvhfZzXm/ap4X =90Rv -----END PGP SIGNATURE-----
