From: Thomas Lord <lord@basiscraft.com>
To: help-gnu-emacs@gnu.org
Subject: are there hooks for text becoming visible or hidden in a given window?
Date: Thu, 24 Feb 2022 14:25:39 -0800 [thread overview]
Message-ID: <06e7c939da37479902e9a935fbaf487a@basiscraft.com> (raw)
Dear Emacs Lisp hackers,
Is there a way to mark a region of text in a buffer, so that when that
text becomes visible in any window, or when it stops being visible, a
hook is called and provided the location of the text in the buffer, and
the window in which its visibility has changed?
I would like to implement a feature that when certain text changes
visibility, the contents of separate buffer are automatically changed.
For example, if a markdown image link scrolls into view in one buffer,
the image itself would appear in a second window, but disappear from the
second window if the link is deleted or scrolled outside of the window.
I couldn't find anything like this and I don't see a clean alternative.
Watching scroll events would only cover part of the problem and I'm
worried about the interactive performance of having to frequently search
the range of visible text for text with a certain property or within a
certain overlay.
Thanks,
-t
next reply other threads:[~2022-02-24 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 22:25 Thomas Lord [this message]
2022-02-25 0:10 ` are there hooks for text becoming visible or hidden in a given window? Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-25 7:07 ` Eli Zaretskii
2022-02-25 20:51 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-25 2:42 ` Michael Heerdegen
2022-02-25 7:04 ` Eli Zaretskii
2022-02-26 21:42 ` Thomas Lord
2022-02-27 0:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=06e7c939da37479902e9a935fbaf487a@basiscraft.com \
--to=lord@basiscraft.com \
--cc=help-gnu-emacs@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.
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).