From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Clément Pit--Claudel" <clement.pit@gmail.com>, emacs-devel@gnu.org
Subject: Re: Redisplay hook
Date: Mon, 04 Jul 2016 03:55:05 -0400 [thread overview]
Message-ID: <jwvmvlx978s.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83twg6p1kd.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 Jul 2016 05:41:22 +0300")
> Blocking input is not enough (and is just a workaround for problems
> you had, anyway). But before we discuss this seriously, I have a
> feeling that such a hook was already discussed in the past, and we
> found it unnecessary and/or dangerous. Stefan, do you remember
> something like that?
I don't have a clear recollection either, sorry.
I guess part of the question is what would be the use of such a hook.
The difference between a pre-redisplay-hook and a
post-redisplay-hook is not very large since most of the result of
redisplay is "invisible" to Elisp. The main differences I can think of
would be:
- jit-lock stuff, in case you want to see the buffer after jit-locking.
but it seems you can just as well hook into jit-lock to get
that result.
- scrolling, in case you want to react to changes in the user-visible
window-start/end.
Of course the use could be fairly tricky, with risks of the
post-redisplay-hook causing further redisplay-cycle ad-nauseam, but we
already have this problem with the window-scroll-functions, IIRC.
Stefan
next prev parent reply other threads:[~2016-07-04 7:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 19:24 Redisplay hook Clément Pit--Claudel
2016-07-03 3:27 ` Eli Zaretskii
2016-07-03 4:36 ` Clément Pit--Claudel
2016-07-03 7:45 ` Eli Zaretskii
2016-07-03 14:23 ` Clément Pit--Claudel
2016-07-03 14:51 ` Clément Pit--Claudel
2016-07-03 15:37 ` Eli Zaretskii
2016-07-04 0:05 ` Clément Pit--Claudel
2016-07-04 2:41 ` Eli Zaretskii
2016-07-04 4:31 ` Clément Pit--Claudel
2016-07-04 14:47 ` Eli Zaretskii
2016-07-04 16:14 ` Clément Pit--Claudel
2016-07-04 16:24 ` Eli Zaretskii
2016-07-04 7:55 ` Stefan Monnier [this message]
2016-07-04 14:52 ` Eli Zaretskii
2016-07-04 16:07 ` Clément Pit--Claudel
2016-07-04 20:37 ` Robert Weiner
2016-07-04 21:00 ` Clément Pit--Claudel
2016-07-04 21:28 ` Robert Weiner
2016-07-04 21:50 ` Clément Pit--Claudel
2016-07-04 21:29 ` Drew Adams
2016-07-04 21:36 ` Clément Pit--Claudel
2016-07-04 21:57 ` raman
2016-07-04 22:11 ` Clément Pit--Claudel
2016-07-05 22:59 ` Richard Stallman
2016-07-05 23:47 ` Clément Pit--Claudel
2016-07-03 22:34 ` Richard Stallman
2016-07-04 0:09 ` Clément Pit--Claudel
2016-07-04 2:42 ` Eli Zaretskii
2016-07-04 0:22 ` Mark Oteiza
2016-07-04 2:42 ` Eli Zaretskii
2016-07-04 7:59 ` Andreas Schwab
2016-07-04 14:52 ` Eli Zaretskii
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=jwvmvlx978s.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=clement.pit@gmail.com \
--cc=eliz@gnu.org \
--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.