all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: What's the best (i.e. least bad) way to re-redisplay?
Date: Mon, 30 Aug 2021 18:10:46 +0000	[thread overview]
Message-ID: <YS0fJqZsaSrxRje+@ACM> (raw)
In-Reply-To: <83r1egu2xx.fsf@gnu.org>

Hello, Eli and Stefan.

On Thu, Aug 26, 2021 at 09:37:14 +0300, Eli Zaretskii wrote:
> > Date: Wed, 25 Aug 2021 20:09:24 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: emacs-devel@gnu.org

> > > I think something along the lines of

> > >     (run-with-timer 0 nil
> > >                     (lambda (buf)
> > >                       (with-current-buffer buf (font-lock-flush)))
> > >                     (current-buffer))

> > > is the cleanest that comes to mind.

> > Thanks.  That's probably cleaner than a direct use of
> > jit-lock-force-redisplay.

> Why is it cleaner?  jit-lock and font-lock include provision for the
> fontification function to tell jit-lock what was the region actually
> fontified, and that will trigger a call to jit-lock-force-redisplay in
> a timer.  Why not use an existing mechanism?

In the end, I coded up a direct use of jit-lock-force-redisplay in a
one-time timer.  The reason I preferred this over font-lock-flush is that
j-l-f-r says in its doc string that it forces a redisplay, whereas f-l-f
merely says it declares (BEG END) as being out of date.

I hope to post my proposed new code on emacs-devel soon.

-- 
Alan Mackenzie (Nuremberg, Germany).



      parent reply	other threads:[~2021-08-30 18:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 18:41 What's the best (i.e. least bad) way to re-redisplay? Alan Mackenzie
2021-08-23 19:35 ` Eli Zaretskii
2021-08-23 19:57   ` Eli Zaretskii
2021-08-24 10:56   ` Alan Mackenzie
2021-08-24 22:43 ` Stefan Monnier
2021-08-25 20:09   ` Alan Mackenzie
2021-08-25 20:36     ` Stefan Monnier
2021-08-26  6:37     ` Eli Zaretskii
2021-08-26 13:49       ` Stefan Monnier
2021-08-26 17:02         ` Alan Mackenzie
2021-08-26 19:27           ` Stefan Monnier
2021-08-30 18:10       ` Alan Mackenzie [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YS0fJqZsaSrxRje+@ACM \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.