unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: David Reitter <david.reitter@gmail.com>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>,
	6154@debbugs.gnu.org, nathaniel.cunningham@gmail.com
Subject: bug#6154: error from: describe-face font-lock-*
Date: Mon, 10 May 2010 23:21:07 -0400	[thread overview]
Message-ID: <yxqeihjjf8c.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <56843DC6-2E52-4BCD-8095-441ECD981063@gmail.com> (David Reitter's message of "Mon\, 10 May 2010 19\:04\:56 -0400")

David Reitter <david.reitter@gmail.com> writes:

> On May 10, 2010, at 11:37 AM, Stefan Monnier wrote:
>
>>> `describe-face' assumes that `find-lisp-object-file-name' always
>>> returns a file name.  I'm seeing the bug described below because we're
>>> pre-loading font-lock and this function returns `C-source'.
>> 
>> All faces are defined in Lisp code, AFAIK, so the value `C-source' is
>> not a correct one.  Without knowing how it happened, it's hard to tell
>> where the problem should be fixed.
>
> Perhaps "pre-loading font-lock" was not enough of a hint in my report.
>
> With a recent Emacs 23 branch checkout:
>
> add a lisp/site-load.el file with the contents
>
> (load "font-lock")

Why would you do that?  font-lock is loadup.el.

> then re-build.
>
> Then, Emacs -Q, and
>
> M-x describe-face RET font-lock-comment-face RET
>
> will produce the error.  Trace, again, below.
>
>
> So:
>
> The `find-lisp-object-file-name' should probably return "font-lock.el" instead of `C-source'.
>
> `describe-face' will break as it is should a face ever be defined in C.  See patch.
>
>
>
>
> Debugger entered--Lisp error: (wrong-type-argument stringp C-source)
>   file-name-nondirectory(C-source)
>   describe-face((font-lock-comment-face))
>   call-interactively(describe-face t nil)
>   execute-extended-command(nil)
>   call-interactively(execute-extended-command nil nil)





  reply	other threads:[~2010-05-11  3:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <h2m20ecf6c71005092257vefcec2ffv4a4b79c39e9294e@mail.gmail.com>
2010-05-10 13:58 ` bug#6154: error from: describe-face font-lock-* David Reitter
2010-05-10 15:37   ` Stefan Monnier
2010-05-10 23:04     ` David Reitter
2010-05-11  3:21       ` Dan Nicolaescu [this message]
2010-05-11  3:43         ` David Reitter
2011-07-09 18:23           ` Glenn Morris

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yxqeihjjf8c.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=6154@debbugs.gnu.org \
    --cc=david.reitter@gmail.com \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=nathaniel.cunningham@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).