unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: are there hooks for text becoming visible or hidden in a given window?
Date: Thu, 24 Feb 2022 19:10:39 -0500	[thread overview]
Message-ID: <jwva6ef7r4p.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 06e7c939da37479902e9a935fbaf487a@basiscraft.com

> 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?

To detect when a chunk of buffer is visible, you can use jit-lock.
It's not exact (it will sometimes trigger even if the chunk is not
actually visible), but it's probably the closest we have (especially if
you want it to be efficient even where there are thousands of such
buffer-chunks to "monitor").

> but disappear from the second window if the link is deleted or
> scrolled outside of the window.

We don't have anything for that, no.  I'd suggest you use
a post-command-hook that monitors which of those thingies is
still visible.

I have been known to propose the introduction of
a `post-redisplay-function` which would work like
`pre-redispay-function` except it's run after the redisplay.
I think I have a patch for that lying around (IIRC originally written
to try and improve the display of "tofu" by adding a `help-echo`
property to those characters).

I guess you could use such a thing as well (and potentially for both
uses).  Changing a buffer in response to changes to the display of
another window isn't well supported by the redisplay (because it means
you need a redisplay cycle right after a redisplay cycle), so you'd need
to force a new redisplay "by hand".

There might also be some questions about what "visible" means.
E.g. is a chunk of buffer "visible" if it's between `window-start` and
`window-end` but is covered by an `invisible` property?  Or if it's
(horizontally) scrolled out of view?


        Stefan




  reply	other threads:[~2022-02-25  0:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 22:25 are there hooks for text becoming visible or hidden in a given window? Thomas Lord
2022-02-25  0:10 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
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=jwva6ef7r4p.fsf-monnier+emacs@gnu.org \
    --to=help-gnu-emacs@gnu.org \
    --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.
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).