From: Jambunathan K <kjambunathan@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15312@debbugs.gnu.org
Subject: bug#15312: Info (point-entered, point-left): Doc incomplete, hence incorrect
Date: Fri, 13 Sep 2013 21:50:20 +0530 [thread overview]
Message-ID: <87k3ikn16j.fsf@gmail.com> (raw)
In-Reply-To: <jwvppscpxpi.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 13 Sep 2013 11:15:10 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> 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.
(mapc
(lambda (s)
(insert (propertize s 'mouse-face font-lock-comment-face)))
'("ab" "cd"))
The intention of the programmer in the above case MAY have been to treat
"ab" and "cd" differently.
But the way Emacs deals with them, it considers "abcd" as a single
stretch and they are highlighted together.
(insert (propertize "ab" 'mouse-face font-lock-comment-face))
(insert (propertize "cd" 'mouse-face font-lock-function-name-face))
> 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".
I don't really don't treat documentation as bible, because I am not a
Christian. Actually I am a pagan.
My argument is that and has been this:
1. Documentation is incomplete.
2. IRL, two hotels belonging to different owners sitting on adjacent
plots is unlikely look the same and painted the with same color.
I don't consider implementation as buggy. Implementation has it's
limitations but the limitations are reasonable.
The limitations should be documented. Also, there are gotchas.
3. In a parsed-context, the parser can easily identify "the span" of a
given character. So insisting that there be text properties other
than point-entered could be limiting.
In the example cited, the point-entered propery is ALWAYS ON meaning
it is mode-local or buffer-local.
> Stefan
next prev parent reply other threads:[~2013-09-13 16:20 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
2013-09-13 16:20 ` Jambunathan K [this message]
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=87k3ikn16j.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=15312@debbugs.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.
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).