On 11 Oct 2000, Yoshiki Hayashi <yoshiki(a)xemacs.org> wrote:
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp>
> (1) Custom is _full_ of calls to reset-face type functions that
> destroy user customizations unless they were made through Custom.
Not in this case. Suppose you use Alexander's .emacs and
opened a new frame. As he wrote, it's shown in default
face. Then evaluate (setq frame-background-mode 'dark) and
open another frame. It's displayed in right faces.
Not in my case. I still see the same effects. I end up with the
font-lock-comment-face being cyan in the second frame, while it's green
in the first frame.
I made sure that `frame-background-mode' was set correctly, as well. It
seemed to be right.
> I think adjusting faces with respect to the default face's
> is a very bad idea as a basic function; it should be done at a very
> high level, such as Custom themes. At lower levels, functions should
> do what the user says.
Hmm... Then what background spec of defface is for? I'm
not a particular fun of it, but I think it's useful.
I think that the big issue is that the software continues to adapt
itself to the default background color, despite my telling explicitly
what I want.
I think that if I only set the default face, having XEmacs change the
rest of it's faces to something readable is nice. When I explicitly set
the face properties, I would expect them to stay, even if that's
We fear that pop-culture is the only culture we're ever going to have.
We want to stop reading magazines, stop watching tv, stop caring about
Hollywood, but we're addicted to the things we hate.
-- KMFDF, _Dogma_