unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
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, 04 Jul 2016 20:02:53 +0300	[thread overview]
Message-ID: <834m85pc8y.fsf@gnu.org> (raw)
In-Reply-To: <577A9156.9070007@gmail.com> (message from Clément Pit--Claudel on Mon, 4 Jul 2016 12:39:50 -0400)

> 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.



  reply	other threads:[~2016-07-04 17:02 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 [this message]
2016-07-04 17:15   ` Clément Pit--Claudel
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

  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=834m85pc8y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=clement.pit@gmail.com \
    --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 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).