all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: What's the best (i.e. least bad) way to re-redisplay?
Date: Mon, 23 Aug 2021 18:41:59 +0000	[thread overview]
Message-ID: <YSPr9wCrrjxRAEqb@ACM> (raw)

Hello, Emacs.

I'm currently thinking about issues raised in the thread "cc-mode
fontification feels random" in June.

I envisage a situation where an identifier is identified as a type during
jit-lock fontification, and thus font-lock-type-face needs to be applied
to all occurrences of this identifier.

The problem is, there will be occurences in the foreground window before
the one which triggered the fontification.  Redisplay will already have
passed this earlier buffer position.  So I need to trigger another
redisplay immediately after the current one.

What is the least bad way of doing this?

Currently, I'm thinking of something like the CC Mode fontification
functions setting a flag, and a repeating timer function testing this
flag every 0.025s, say, and triggering a redisplay if it's set.

One problem is knowing whether or not redisplay is currently active.  Is
there a simple way to do this in Lisp?  (I know there is in C.)

I surely can't be the first person needing to do this sort of thing.
Suggestions and comments, please, from the wise.  :-)

-- 
Alan Mackenzie (Nuremberg, Germany).



             reply	other threads:[~2021-08-23 18:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 18:41 Alan Mackenzie [this message]
2021-08-23 19:35 ` What's the best (i.e. least bad) way to re-redisplay? 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

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=YSPr9wCrrjxRAEqb@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@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.