Comment 3 for bug 320886

Interesting. I wasn't aware of that change. I humbly submit that this sucks. It arbitrarily breaks a working system and will be a rude surprise for those who weren't expecting it.

Unfortunately, I have a dissertation to write intead of patch the X server code responsible for this misbheavior, but I think the following algorithms would be significantly better for transition and perhaps in general. I understand why the -hostname dependent behavior was wanted, but it lacks a bit of flourish yet.

Algorithm 1:
1) If $HOME/.Xdefaults-hostname exists, read it in.
2) Else, if $HOmE/.Xdefaults exists, read it in.

This won't break backwards compatibility and has an added feature: if you migrate your Xdefaults to a new host or whatever, a "default" Xdefaults file will be available..

Alrigthm 2:
1) If $HOME/.Xdefaults exists, read it in.
2) If $HOME/.Xdefaults-hostname exists, read it in and override any conflicts with $HOME/.Xdefaults.

This has all of the advantages of algo 1 but now even allows you to set up a generic Xdefaults file with per-box customizations in the -hostname file.

Personally, I'm a fan of Algo 2 and would recommend someone implement it before Jaunty goes stable, or both of us users of this feature will be upset. ;)