From: Eli Zaretskii <eliz@gnu.org>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: problem with font lock
Date: Fri, 15 Jan 2010 16:43:21 +0200 [thread overview]
Message-ID: <83ljfz77jq.fsf@gnu.org> (raw)
In-Reply-To: <87zl4fftv2.fsf@newton.homeunix.net>
> From: "Jose A. Ortega Ruiz" <jao@gnu.org>
> Date: Fri, 15 Jan 2010 13:14:09 +0100
>
> i'm experiencing an intermittent problem with font lock that i don't
> know how to debug (this is emacs 23.1.91 packaged for debian). every now
> and then, font lock just stops working in most (but not all) of the
> buffers: the extant colors remain, but new text is not coloured at all
> (e.g., if i comment a line out, the line's text retains its initial
> faces instead of switching to the comment face). as i said, i haven't
> found a way to reproduce this behaviour deterministically, and when it
> starts happening i don't see any error message around. so my question
> is: what would you recommend to look at when i enter this state, so that
> i can submit a useful bug report?
Did you customize font-lock or jit-lock in any way? Does this happen
in "emacs -Q"? If you type "M-x font-lock-fontify-buffer RET", after
e.g., commenting a line, does the fontification catch up with the
changes?
Re-fontification when the buffer is modified or scrolled is done by
jit-lock.el, and it generally runs off Emacs timers. So anything that
prevents times from running would have the effect that you seem to
observe.
next prev parent reply other threads:[~2010-01-15 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 12:14 problem with font lock Jose A. Ortega Ruiz
2010-01-15 14:19 ` Stefan Monnier
2010-01-19 21:54 ` Jose A. Ortega Ruiz
2010-01-15 14:43 ` Eli Zaretskii [this message]
2010-01-15 16:27 ` Jose A. Ortega Ruiz
2010-01-15 17:49 ` Stefan Monnier
2010-01-15 16:24 ` alin.s
2010-01-15 20:15 ` Jose A. Ortega Ruiz
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=83ljfz77jq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jao@gnu.org \
/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.