Georg Nikodym <georgn(a)canada.sun.com> writes:
Thanks for the excellent advice, but my font-menu-this-frame-only-p
is
set to t (through no deliberate act of my own) and I still see the
weirdness.
Here it works. Note that when font-menu-this-frame-only-p is t the
code is exactly the same as the old font menu the new custom related
code is only invoked when font-menu-this-frame-only-p is nil.
Funny that font-menu-this-frame-only-p is t for you. It defaults to
nil.
Now, I hazard to point out that changing the _font_ appears to work
but _size_ changes appear to be global...
Hmmm, not that simple either. Changing _font_ in this VM compose
frame to Bembo worked. Changing size to 14 resulted in this frame
changing OK, my "main" frame's "Help" buffer to change to bembo
at
size 14 and my VM frame to entirely to bembo 14.
Can you reproduce this with xemacs -vanilla and just scratch buffers?
Secondly. You are running with the latest version of x-font-menu.el ?
In particular one that has this snippet
;; If we need to be frame local we do the changes ourselves.
(if font-menu-this-frame-only-p
;;; WMP - we need to honor font-menu-this-frame-only-p here!
(set-face-font 'default new-default-face-font
(and font-menu-this-frame-only-p (selected-frame)))
;; OK Let Customize do it.
(when (and family (not (equal family from-family)))
(setq new-props (append (list :family family) new-props)))
Without this change I can understand the behaviour but if you are
really running the latest I am at a loss.
Jan