Bug 125617 - app-emacs/color-theme "Wrong type argument: symbolp,..." error
Bug#: 125617 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: All Status: RESOLVED Severity: normal Priority: P2
Resolution: FIXED Assigned To: emacs@gentoo.org Reported By: paul@wolfbone.ath.cx
Component: Applications
URL:  http://www.emacswiki.org/cgi-bin/wiki/ColorTheme
Summary: app-emacs/color-theme "Wrong type argument: symbolp,..." error
Keywords:  
Status Whiteboard: 
Opened: 2006-03-09 09:17 0000
Description:   Opened: 2006-03-09 09:17 0000
I think this bug affects only emacs-cvs users. It did mine and I found the
following fix for it at emacswiki.org:

     (defun color-theme-face-attr-construct (face frame)
       (if (atom face)
           (custom-face-attributes-get face frame)
         (if (and (consp face) (eq (car face) 'quote))
             (custom-face-attributes-get (cadr face) frame)
           (custom-face-attributes-get (car face) frame)))))

------- Comment #1 From Matthew Kennedy (RETIRED) 2006-05-15 09:16:32 0000 -------
Which emacs port? (app-editors/emacs or app-editors/emacs-cvs).  Could you try
starting emacs with --debug-init and post the backtrace here?  It sounds like a
return of the old easy-menu bug.

------- Comment #2 From P.L.Hayes 2006-05-15 09:58:23 0000 -------
I'm using emacs-cvs but it's a color-theme bug; it has been fixed in
color-theme cvs and the fix put up on emacswiki:

http://www.emacswiki.org/cgi-bin/wiki/ColorTheme#toc6

With --debug-init (after commenting out the fix in my .emacs) nothing different
happened. I guess --debug-init only deals with errors occurring strictly within
the init file. When I started color-theme-select I got an *error message, as
expected, but nothing else happened. I could trace the relevant functions and
describe what happens and put the output here and figure out why the above code
fixes it but is that really necessary? 

* face-attribute: Wrong type argument: symbolp,
(font-latex-doctex-documentation-face font-lock-preprocessor-face)

------- Comment #3 From Matthew Kennedy (RETIRED) 2006-08-07 21:59:05 0000 -------
version 6.6.0 was added to portage which should resolve this bug,