From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@suse.de>
Cc: mvoteiza@udel.edu, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Redisplay hook
Date: Mon, 04 Jul 2016 17:52:47 +0300 [thread overview]
Message-ID: <83furppi9s.fsf@gnu.org> (raw)
In-Reply-To: <mvm1t394yvx.fsf@hawking.suse.de> (message from Andreas Schwab on Mon, 04 Jul 2016 09:59:30 +0200)
> From: Andreas Schwab <schwab@suse.de>
> Cc: Mark Oteiza <mvoteiza@udel.edu>, rms@gnu.org, emacs-devel@gnu.org
> Date: Mon, 04 Jul 2016 09:59:30 +0200
>
> >> Well, pre-redisplay-functions already exists, and it appears to be a hook
> >> with equal potential for making trouble.
> >
> > No, because it runs _before_ redisplay.
>
> But a post-redisplay hook should not be any more dangerous than a
> post-command hook. Like the latter it could just be disabled
> automatically if anything went wrong.
It's not much more dangerous, by and large, but I think it's slightly
more dangerous, because it will most probably run from within the
display code, and thus runs the risk of triggering an infinite
redisplay loop. By contrast, a post-command hook cannot trigger
another post-command hook (AFAIU).
prev parent reply other threads:[~2016-07-04 14:52 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
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 [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
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=83furppi9s.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mvoteiza@udel.edu \
--cc=rms@gnu.org \
--cc=schwab@suse.de \
/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).