unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Need help with search based font-locking
Date: Wed, 23 Dec 2009 22:07:10 -0500	[thread overview]
Message-ID: <jwvbphp2iam.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87637yj64c.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Wed, 23 Dec 2009 12:13:07 +0100")

>   (let (font-lock-set-defaults) (font-lock-set-defaults))
>   (jit-lock-refontify (point-min) (point-max))
>   (redisplay t)

This assumes lots of things about font-lock's implementation (including
the use of jit-lock).
A slightly less invasive implementation would be:

  (font-lock-mode -1)
  (kill-local-variable 'font-lock-set-defaults)
  (font-lock-mode 1)

tho the `font-lock-set-defaults' bit is still ugly.

So, I'd recommend you submit a patch which adds a new function that does
the above 3 steps (call it `font-lock-refresh-all' or something), and
then use that one.

In your case, tho, a better option might be to change your
greql-font-lock-keywords-3 so it doesn't change.
See sh-font-lock-here-doc for an example of how you might be able to do
that.  Admittedly, this may not always work because it may depend on the
order the hilighting is done (and this order is not necessarily
sequential for font-lock-keywords).  So you may need to move some of the
work (the one that modifies the match regexp) to
font-lock-syntactic-keywords (which is guaranteed to be applied
sequentially).


        Stefan





  parent reply	other threads:[~2009-12-24  3:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 21:45 Need help with search based font-locking Tassilo Horn
2009-12-22 22:43 ` Lennart Borgman
2009-12-23 11:13   ` Tassilo Horn
2009-12-23 11:38     ` Tassilo Horn
2009-12-24  3:07     ` Stefan Monnier [this message]
2009-12-24  3:45       ` Lennart Borgman
2009-12-24  4:46         ` Stefan Monnier
2009-12-24 13:48           ` Lennart Borgman
2009-12-28 13:20             ` Tassilo Horn
2009-12-28 13:54               ` Lennart Borgman
2009-12-28 18:18                 ` Tassilo Horn
2009-12-30 13:56       ` Tassilo Horn
2009-12-30 15:29         ` Stefan Monnier

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=jwvbphp2iam.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@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 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).