From: Karl Kleinpaste <karl@charcoal.com>
Subject: font-lock-verbose error
Date: Sat, 12 Jan 2002 13:43:32 -0500 [thread overview]
Message-ID: <vxkbsfzfm0b.fsf@cinnamon.vanillaknot.com> (raw)
In the last day or so, I am getting this when trying to send mail:
Symbol's value as variable is void: font-lock-verbose
(1) (warning/warning) Error caught in `font-lock-pre-idle-hook': (void-variable font-lock-verbose)
Signaling: (void-variable font-lock-verbose)
font-lock-fontify-buffer()
font-lock-mode(1)
turn-on-font-lock()
run-hooks(turn-on-font-lock)
derived-mode-run-hooks(message-mode)
message-mode()
message-pop-to-buffer("*mail*")
message-mail()
gnus-summary-mail-other-window(nil)
call-interactively(gnus-summary-mail-other-window)
What's weird about this is that, having grep'd the entirety of XEmacs'
xemacs/packages/lisp/*.el for font-lock-verbose, I don't find it
defined anywhere. I would guess this is something to report on
xemacs-beta, yes?
In any event, a simple workaround is simply to set font-lock-verbose.
The only recent mention of font-locking in Changelog is ShengHuo's
January 10th comment.
next reply other threads:[~2002-01-12 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 18:43 Karl Kleinpaste [this message]
2002-01-12 19:02 ` Lars Magne Ingebrigtsen
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=vxkbsfzfm0b.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.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.
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 NNTP newsgroup(s).