From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: martin rudalics <rudalics@gmx.at>, emacs-devel@gnu.org
Subject: Re: diary font-lock issue
Date: Wed, 17 May 2006 11:11:13 -0400 [thread overview]
Message-ID: <jwvves4snoz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <1hac9hn99k.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 16 May 2006 13:56:39 -0400")
> This all seems very complex. According to:
> <http://lists.gnu.org/archive/html/emacs-devel/2006-04/msg00881.html>
> "the font-lock-multiline property should be enough in all cases to
> make it unnecessary to use an after-change-function hook."
That's true. His after-change-function is not needed.
> That's a long thread, but AFAICS, it seems that for simple keyword
> fontification, setting font-lock-multiline for the buffer ought to be
> enough.
No. font-lock-multiline (just like after-change-functions) only help with
the re-fontification of multiline keywords. The problem you're facing is
the one of initial detection of a multiline keyword.
> (Indeed, the fancy diary buffer is not something one edits, so this is
> about as simple as multiline font-lockign can get.)
Actually the initial detection of multiline keywords is the hard part, not
the re-fontification after a buffer change.
Note that a workaround for your problem is to turn off jit-lock (you can do
so buffer-locally by setting font-lock-support-mode to nil).
Stefan
next prev parent reply other threads:[~2006-05-17 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 7:22 diary font-lock issue Glenn Morris
2006-05-16 15:50 ` martin rudalics
2006-05-16 17:56 ` Glenn Morris
2006-05-16 21:42 ` martin rudalics
2006-05-17 15:11 ` Stefan Monnier [this message]
2006-05-17 15:05 ` Stefan Monnier
2006-05-17 19:11 ` Glenn Morris
2006-05-17 21:15 ` Stefan Monnier
2006-05-21 10:39 ` martin rudalics
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=jwvves4snoz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).