From: David Reitter <david.reitter@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: nathaniel.cunningham@gmail.com, 6154@debbugs.gnu.org
Subject: bug#6154: error from: describe-face font-lock-*
Date: Mon, 10 May 2010 19:04:56 -0400 [thread overview]
Message-ID: <56843DC6-2E52-4BCD-8095-441ECD981063@gmail.com> (raw)
In-Reply-To: <jwvk4rbdb2z.fsf-monnier+emacs@gnu.org>
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")
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)
next prev parent reply other threads:[~2010-05-10 23:04 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 [this message]
2010-05-11 3:21 ` Dan Nicolaescu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56843DC6-2E52-4BCD-8095-441ECD981063@gmail.com \
--to=david.reitter@gmail.com \
--cc=6154@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.