(please copy me on replies)
> OK, try
> xemacs -q
> and eval
> (progn
> (set-face-foreground 'default "white")
> (set-face-background 'default "midnightblue")
> (require 'font-lock)
> (set-face-foreground 'font-lock-comment-face "#ff8080"))
> now load a .el file. note the comment color.
> C-x 5 2
> and note the different comment color.
Andy>
Andy> The bizarre thing is that if you create additional frames they come up in
Andy> the correct color briefly and then switch to the wrong ones.
OK try this:
(require 'font-lock)
=> font-lock
(face-property 'font-lock-comment-face 'foreground 'all)
=> ((global (nil . "blue4")))
(set-face-background 'default "red")
=> "red"
(face-property 'font-lock-comment-face 'foreground 'all)
=> ((global (nil . "blue4")))
(set-face-foreground 'font-lock-comment-face "white")
=> "white"
(face-property 'font-lock-comment-face 'foreground 'all)
=> ((global (nil . "white")))
(make-frame)
=> #<mswindows-frame "XEmacs" 0xcdd>
(face-property 'font-lock-comment-face 'foreground 'all)
=> ((#<mswindows-frame "XEmacs" 0xcdd> (nil . "gray80"))
(global (nil . "white")))
Creating the frame is adding all these frame-specific color specifiers
for the new frame onto the face. WTF!?
Greg