From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 15312@debbugs.gnu.org, kjambunathan@gmail.com
Subject: bug#15312: Info (point-entered, point-left): Doc incomplete, hence incorrect
Date: Mon, 16 Sep 2013 20:10:41 +0300 [thread overview]
Message-ID: <83vc20pu9a.fsf@gnu.org> (raw)
In-Reply-To: <jwvk3ig21ka.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: kjambunathan@gmail.com, 15312@debbugs.gnu.org
> Date: Mon, 16 Sep 2013 12:15:27 -0400
>
> > Perhaps we need to step back and talk about the situations where these
> > hooks are supposed to be used. Because I cannot see any sense in
> > calling the hooks when the values of these properties don't change.
>
> Agreed, but the code also runs the hook when the value of the
> `point-entered' does not change but the value of some unrelated
> property changes. That is an error.
Of course. But I was trying to say that we should formulate a clear
specification for when these hooks shall be called. What the manual
says now makes little sense to me (and is also somewhat vague).
> >> The right thing to do is to declare point-entered and point-left
> >> properties as obsolete and replace them by something like cursor-entered
> >> and cursor-left properties which are only checked at command boundaries
> >> (or better, checked just before redisplay).
> > Redisplay can be forced as part of a command.
>
> I know, and I think that for most uses of these kinds of properties we'd
> also want to run the hook when redisplay is called in the middle of
> a command (e.g. in the middle of query-replace). Note that we'd probably
> also want to run the hook when redisplay is short-circuited by pending input.
Calling this from redisplay might need some non-trivial protocol,
because the hook can legitimately move point, which will re-enter
redisplay, which will call the hook...
next prev parent reply other threads:[~2013-09-16 17:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 13:34 bug#15312: Info (point-entered, point-left): Doc incomplete, hence incorrect Jambunathan K
2013-09-09 16:37 ` Eli Zaretskii
2013-09-10 3:33 ` Jambunathan K
2013-09-10 3:40 ` Jambunathan K
2013-09-10 15:18 ` Eli Zaretskii
2013-09-11 9:55 ` Jambunathan K
2013-09-11 13:42 ` Eli Zaretskii
2013-09-13 5:22 ` Jambunathan K
2013-09-13 6:15 ` Jambunathan K
2013-09-13 8:02 ` Eli Zaretskii
2013-09-13 10:28 ` Jambunathan K
2013-09-13 13:12 ` Stefan Monnier
2013-09-13 13:29 ` Eli Zaretskii
2013-09-13 15:15 ` Stefan Monnier
2013-09-13 15:59 ` Eli Zaretskii
2013-09-13 16:28 ` Stefan Monnier
2013-09-13 16:42 ` Jambunathan K
2013-09-13 16:45 ` Eli Zaretskii
2013-09-13 17:18 ` Stefan Monnier
2013-09-13 19:26 ` Eli Zaretskii
2013-09-13 20:32 ` Stefan Monnier
2013-09-14 6:48 ` Eli Zaretskii
2013-09-16 16:15 ` Stefan Monnier
2013-09-16 17:10 ` Eli Zaretskii [this message]
2013-09-13 16:20 ` Jambunathan K
2013-09-13 16:43 ` Eli Zaretskii
2013-09-13 17:19 ` Stefan Monnier
2013-09-13 19:27 ` Eli Zaretskii
2013-09-13 20:35 ` Stefan Monnier
2013-09-14 6:50 ` Eli Zaretskii
2013-09-13 8:03 ` Eli Zaretskii
2013-09-14 6:35 ` Jambunathan K
2013-11-15 5:04 ` Jambunathan K
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=83vc20pu9a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15312@debbugs.gnu.org \
--cc=kjambunathan@gmail.com \
--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).