unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eric Abrahamsen'" <eric@ericabrahamsen.net>,
	"'Eli Zaretskii'" <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: RE: overlays vs text properties
Date: Wed, 13 Jul 2011 07:55:51 -0700	[thread overview]
Message-ID: <A0362EB3D3184D4FB3E8D7FC81D81AE3@us.oracle.com> (raw)
In-Reply-To: <87tyaqiqz8.fsf@ericabrahamsen.net>

I don't have much to offer here that hasn't been said already.

FWIW - It sounds to me like overlays are best suited for what you want to do.

Checking for point movements in/out of the overlay: How often and when do you
need to do it?

If you need to do it after each user interaction, then maybe do it in
`post-command-hook'.  If you can avoid using that hook, great (it tends to be
overused, in general).  But if that's when you need to check, then that's
probably the best approach I can think of.

(To check, just see whether point is inside the overlay.  To know whether that
state represents a change you will likely need to save the last in/out state and
compare.)




      parent reply	other threads:[~2011-07-13 14:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13  6:12 overlays vs text properties Eric Abrahamsen
2011-07-13  6:59 ` Eli Zaretskii
2011-07-13  7:23   ` Eric Abrahamsen
2011-07-13  7:28     ` Eli Zaretskii
2011-07-13  7:32       ` Eric Abrahamsen
2011-07-13  8:07         ` PJ Weisberg
2011-07-13 22:21           ` Eric Abrahamsen
2011-07-13  9:57         ` Eli Zaretskii
2011-07-13 14:55     ` Drew Adams [this message]

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=A0362EB3D3184D4FB3E8D7FC81D81AE3@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --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).