all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 13 Sep 2013 18:59:26 +0300	[thread overview]
Message-ID: <83six8hfvl.fsf@gnu.org> (raw)
In-Reply-To: <jwvppscpxpi.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: kjambunathan@gmail.com,  15312@debbugs.gnu.org
> Date: Fri, 13 Sep 2013 11:15:10 -0400
> 
> > Sorry, I don't understand what you are saying about the original issue
> > with point-entered/left.  Are you saying that the code works
> > correctly, or are you saying it has a bug?
> 
> That the code that uses the `point-entered/left' property (just like
> the code that uses the other mentioned properties like `display',
> `mouse-face', ...) considers runs of characters with the same property
> value as belonging together; which means that the text-property is used
> to specify a kind of interval.

Sorry, I'm still in the dark.  Does the code presented in
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15312#11 work correctly
and as expected, or does it not?  If the latter, what would you expect
that code to do instead?

> Clearly, this disagrees with:
> 
>     ,----  (info "(elisp) Not Intervals")
>     | "What are the properties of this character?"  So we have decided these
>     | are the only questions that make sense; we have not implemented asking
>     | questions about where intervals start or end.
>     `----
> 
> And actually the above text is incorrect/incomplete in the sense that
> next-single-property-change clearly implements a functionality that lets
> you "ask questions about where intervals start or end".

Actually, it doesn't disagree, if you keep in mind what RMS meant when
he wrote that text (intervals can and do overlap, while runs of text
properties cannot).  But IMO that is a completely different issue.
The original issue raised by this report was about point-entered/left
hooks, and the code presented in the above URL illustrates the issue.
I suggest that we solve that issue first.





  reply	other threads:[~2013-09-13 15:59 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83six8hfvl.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.