From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, esq@lawlist.com,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Use cases for post-redisplay hooks
Date: Mon, 4 Jul 2016 13:15:26 -0400 [thread overview]
Message-ID: <577A99AE.3020901@gmail.com> (raw)
In-Reply-To: <834m85pc8y.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1520 bytes --]
On 2016-07-04 13:02, Eli Zaretskii wrote:
>> From: Clément Pit--Claudel <clement.pit@gmail.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>,
>> michael_heerdegen@web.de, esq@lawlist.com
>> Date: Mon, 4 Jul 2016 12:39:50 -0400
>>
>> 2. (Keith David Bershatsky + Michael Heerdegen @ https://lists.gnu.org/archive/html/bug-gnu-emacs/2016-01/msg01013.html) Updating overlays after scrolling. The bug thread is pretty long and subtle, but this issue has also been discussed on emacs.stackexchanged IIRC.
>
> AFAIU, this one is not a candidate for post-redisplay hook. Scrolling
> doesn't happen every redisplay, only some of them; and we already have
> a hook for that.
Ok. I got mislead by this message:
From: Eli Zaretskii
Subject: bug#22404: 25.1.50; Forcing `window-scroll-functions` to run.
Date: Fri, 29 Jan 2016 16:37:16 +0200
> From: Michael Heerdegen <address@hidden>
> Cc: Keith David Bershatsky <address@hidden>, address@hidden
> Date: Fri, 29 Jan 2016 13:00:42 +0100
>
> Anyway, using pre-command-hook is too late for us: it's not executed
> unless the next input arrives, so you have to hit a key until
> decorations or whatever get updated.
Then maybe we need a post-redisplay-hook.
But in that case, it seems that the only two currently identified use cases would be happy with a hook running after redisplay has completed in full. Let's see whether other examples pop up :)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2016-07-04 17:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 16:39 Use cases for post-redisplay hooks Clément Pit--Claudel
2016-07-04 17:02 ` Eli Zaretskii
2016-07-04 17:15 ` Clément Pit--Claudel [this message]
2016-07-04 21:45 ` Stefan Monnier
2016-07-10 22:17 ` Clément Pit--Claudel
2016-07-11 3:34 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2016-07-04 21:42 Keith David Bershatsky
2016-07-04 22:06 ` Stefan Monnier
2016-07-05 2:35 ` Eli Zaretskii
2016-07-04 22:50 Keith David Bershatsky
2016-07-05 8:12 ` Stefan Monnier
2016-07-07 16:08 ` Clément Pit--Claudel
2016-07-05 17:45 Keith David Bershatsky
2016-07-07 17:53 Keith David Bershatsky
2016-07-07 19:44 ` Clément Pit--Claudel
2016-07-07 20:19 Keith David Bershatsky
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=577A99AE.3020901@gmail.com \
--to=clement.pit@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esq@lawlist.com \
--cc=michael_heerdegen@web.de \
--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.