unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: are there hooks for text becoming visible or hidden in a given window?
Date: Fri, 25 Feb 2022 09:04:37 +0200	[thread overview]
Message-ID: <83r17rqvei.fsf@gnu.org> (raw)
In-Reply-To: <06e7c939da37479902e9a935fbaf487a@basiscraft.com> (message from Thomas Lord on Thu, 24 Feb 2022 14:25:39 -0800)

> Date: Thu, 24 Feb 2022 14:25:39 -0800
> From: Thomas Lord <lord@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?

Please clarify what you mean by "visible" in this context.  I mean not
a couple of examples, but an exhaustive, complete definition.

> Watching scroll events would only cover part of the problem

Which part it won't cover, in your opinion?

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

Why do you think this could be expensive?  A typical window doesn't
show too much text.



  parent reply	other threads:[~2022-02-25  7:04 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
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 [this message]
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=83r17rqvei.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).