From: Keith David Bershatsky <esq@lawlist.com>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>
Cc: michael_heerdegen@web.de, Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Use cases for post-redisplay hooks
Date: Mon, 04 Jul 2016 14:42:46 -0700 [thread overview]
Message-ID: <m2k2h1dqqx.wl%esq@lawlist.com> (raw)
I am using a slightly modified version of Emacs that has what I call a `window-start-end-hook`, which lets me draw overlays on just the visible window every command loop. I needs more work, but that is the general idea of the modification.
There are certain movements of point that are not covered by the `window-scroll-functions` hook, so that hook cannot be used reliably for the above-mentioned purpose. And, the hook *may* run more than once each command loop, leading to potentially wasted time spent running an overlay function that will need to run again anyway before the display cycle finishes.
The main concern I had regarding a `post-redisplay-hook` would be that users would add Lisp code to the hook that alters `window-start` and `window-end`, and I felt that an additional check was needed before redisplay finishes to make sure that things are where they should be -- e.g., the cursor location. The key ingredient (for me, at least) would be that the `post-redisplay-hook` should provide guaranteed correct values for `window-start` and `window-end`.
Thanks,
Keith
next reply other threads:[~2016-07-04 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 21:42 Keith David Bershatsky [this message]
2016-07-04 22:06 ` Use cases for post-redisplay hooks Stefan Monnier
2016-07-05 2:35 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2016-07-07 20:19 Keith David Bershatsky
2016-07-07 17:53 Keith David Bershatsky
2016-07-07 19:44 ` Clément Pit--Claudel
2016-07-05 17:45 Keith David Bershatsky
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-04 16:39 Clément Pit--Claudel
2016-07-04 17:02 ` Eli Zaretskii
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
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=m2k2h1dqqx.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=clement.pit@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).