I think that the vectors in face-new-frame-defaults need
to have an additional state, different from `unspecified' and
a specific value. This additional state would be `nothing here'.
If the value in `face-new-frame-defaults' is `unspecified',
it would override the defface with `unspecified'.
If
My comment about a possible bug specific to :inherit was because
evaluating the same expression, namely
(set-face-attribute 'completions-first-difference nil ATTR 'unspecified)
when ATTR is different from :inherit, e.g. :background or :slant, does
work as Drew
My comment about a possible bug specific to :inherit was because
evaluating the same expression, namely
(set-face-attribute 'completions-first-difference nil
ATTR 'unspecified)
when ATTR is different from :inherit, e.g.
The recipe to reproduce the problematic behavior was in Drew's mail:
emacs -q
(setq pop-up-frames t)
M-x list-faces-display
Click mouse-2 on completions-first-difference. It shows Inherit: bold.
M-: (set-face-attribute 'completions-first-difference nil :inherit
That's not what I saw a month ago, when this discussion started. And
Drew confirmed my findings back then.
Actually, I don't remember if I tested and confirmed that it worked for
attributes other than :inherit - my recollection is that Eli tested that and
I took his word for it. But Eli
Then I'm confused. As Juri said (and it works):
`unspecified' does just what it says, i.e. leaves the default frame
value untouched. If you want to change the default for new frames,
you can set the value of this attribute to nil. So this should work
just
Then I'm confused. As Juri said (and it works):
`unspecified' does just what it says, i.e. leaves the default frame
value untouched. If you want to change the default for new frames,
you can set the value of this attribute to nil. So this should work
just
Date: Wed, 20 Jul 2005 20:45:35 +0300
From: Eli Zaretskii [EMAIL PROTECTED]
Cc: emacs-pretest-bug@gnu.org
I'll look into the problem with :inherit when I have time, unless
someone beats me to it.
Perhaps I missed something, but it looks like this is simply
unsupported: we handle most face
1. The doc string of face-spec-reset-face does not explain the FRAME arg.
2. The doc string of set-face-attribute does not agree with that of
internal-set-lisp-face-attribute, which does its work. The former
says that FRAME=nil means change on all frames, but does not
mention that it
