From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: On multi-line font lock
Date: Sat, 16 Sep 2017 09:14:44 -0400 [thread overview]
Message-ID: <jwv1sn6aiuw.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <87zi9uolsy.fsf@udel.edu> (Mark Oteiza's message of "Sat, 16 Sep 2017 08:44:13 -0400")
> I see. I feel that's not really explained in the docs, but I also
> haven't yet looked at the source.
I don't think code should rely on this anyway.
> I get the idea that I could also use syntax rules to apply the
> font-lock-multiline property, so I'll try that as well.
Yes, it's probably easier. This said, the jit-lock delay is not
something specific to mailcap syntax: it's just a preference of yours
and it probably applies to all major modes. So a better fix for this
would be to work on jit-lock to offer an option for
jit-lock-contextually to be instantaneous.
Stefan
prev parent reply other threads:[~2017-09-16 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 0:54 On multi-line font lock Mark Oteiza
2017-09-15 12:49 ` Stefan Monnier
2017-09-16 12:44 ` Mark Oteiza
2017-09-16 13:14 ` Stefan Monnier [this message]
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=jwv1sn6aiuw.fsf-monnier+Inbox@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
--cc=mvoteiza@udel.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).