Bug 50867
Summary: | Xresources and Xdefaults | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michal Jaegermann <michal> |
Component: | XFree86 | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-04-03 22:19:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Jaegermann
2001-08-04 02:17:59 UTC
you may try rxvt-2.7.8-1 Hm, kind of difficult to do that. The last one I see in rawhide is rxvt-2.7.6-4 (or there are many, out of sync, rawhide depositories or I should look for it somewhere else?). What's the latest status of this? 'rxvt' from "skipjack", i.e. rxvt-2.7.8-3, will still read and try to interpret ~/.Xdefaults directly (just use strace to see that), which may be not the greatest thing if this was meant to be preprocessed first, but at least it pays attention what is provided by xrdb. If ~/.Xdefaults is missing then it is pretty insistent on trying to open it or ~/.Xdefaults-<host_name>. My strace shows 504 such attempts. :-) OTOH, contrary to what manpage says in RESOURCES section, a presence of ~/.Xresources file is totally ignored. The is XGetDefault() from the X11 library, which tries to open those files. Oh, I should add that with rxvt-2.7.8-3 defaults from /usr/lib/X11/app-defaults/Rxvt seem to be actually used in a contrast to an older version from the original report. Xresources and .Xresources are the official locations in XFree86 4.x. Anything using .Xdefaults should be changed to use Xresources. Any backward compatiibility hacks that are in place by upstream will remain in place, however it is entirely possible upstream may change this, so Xresources shoulds be migrated to. Actually.... my bad. Upstream _did_ change this - 2 years ago. .Xdefaults died over 2 years ago and we kept it around for legacy compatibility for a while. It is gone now. Closing NOTABUG |