On Mon, 2001-12-17 at 11:47, Hrvoje Niksic wrote:
Possible solutions:
IMHO the simplest immediate solution would be to call the appropriate
Custom calls from `frame-notice-user-settings'. This might be
trickier than it initially seems because of all the hair that takes
place in that function, and because of how complex the face stuff is,
and how complex the Custom face stuff is, and the impedance mismatch
between XEmacs face concepts and Custom face concepts. To quote Ben's
comment in frame-notice-user-settings, "this [...] stuff is a load of
trash, and so is this function we're in." But all in all, it
shouldn't be too hard.
A much nicer solution would be for someone with the time and the
inclination to make defface translate into a proper specifier
specification. It would be an interesting project, and the reward of
deleting `custom-initialize-frame' from the face of the earth would
more than make up for all the hours of effort. :-)
I'm not sure what frame-notice-user-settings is for, but I fixed the
problem for myself by inserting the following five lines into my init.el
file:
(add-hook 'after-init-hook
(lambda ()
(set-frame-property (selected-frame) 'background-mode nil)
(set-frame-property (selected-frame) 'custom-properties nil)
(initialize-custom-faces (selected-frame))))
Is this what you were suggesting should go into
frame-notice-user-settings()?
Could a patch like this get folded into XEmacs?