From: Jambunathan K <kjambunathan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15312@debbugs.gnu.org
Subject: bug#15312: Info (point-entered, point-left): Doc incomplete, hence incorrect
Date: Wed, 11 Sep 2013 15:25:56 +0530 [thread overview]
Message-ID: <87hadrel77.fsf@gmail.com> (raw)
In-Reply-To: <83fvtck8mv.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 10 Sep 2013 18:18:32 +0300")
>> (defun --point-entered (&rest args)
>> (message "entered: %s" args))
>>
>> (defun --point-left (&rest args)
>> (message "left: %s" args))
>>
>> (add-text-properties (point-min) (point-max)
>> '(point-left --point-left
>> point-entered --point-entered))
>
> It is not clear to me where did you expect the hooks to be called,
> based on the documentation.
> Was it for every character?
Based on documentation. Yes, for every char.
> only at point-min and point-max?
No.
> And in any case, why do you assume this is a documentation bug
I am not ASSUMING that it is a doc bug. It IS a doc bug. The doc IS
obviously not matching the implementation.
> as opposed to a bug in the implementation?
Well, if you want to promote this report to a bug in implementation, I
have no reservations. But the onus is in on YOU to argue on what counts
it can be deeemed as a bug in implementation.
next prev parent reply other threads:[~2013-09-11 9:55 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 [this message]
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
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=87hadrel77.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=15312@debbugs.gnu.org \
--cc=eliz@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.
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).