[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Redisplay hook
From: |
Eli Zaretskii |
Subject: |
Re: Redisplay hook |
Date: |
Mon, 04 Jul 2016 17:52:47 +0300 |
> From: Andreas Schwab <address@hidden>
> Cc: Mark Oteiza <address@hidden>, address@hidden, address@hidden
> 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).
Re: Redisplay hook, Richard Stallman, 2016/07/03
Re: Redisplay hook, Mark Oteiza, 2016/07/03
Re: Redisplay hook, Eli Zaretskii, 2016/07/03
Re: Redisplay hook, Andreas Schwab, 2016/07/04
Re: Redisplay hook,
Eli Zaretskii <=