all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Tue, 10 Sep 2013 09:03:56 +0530	[thread overview]
Message-ID: <878uz573kr.fsf@gmail.com> (raw)
In-Reply-To: <83sixej6iz.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 09 Sep 2013 19:37:08 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Jambunathan K <kjambunathan@gmail.com>
>> Date: Mon, 09 Sep 2013 19:04:59 +0530
>> 
>> 
>> The info doc (see below) makes no mention of intervals/text properties.
>> It should mention what intervals.c actually does.
>
> What exactly does it not mention now, 

About text properties.  They need to be different.

> and under which circumstances will a Lisp programmer see that?

Does this question mean when will point-entered and point-left hook be
used (or used at all)?  I suggest that you look at table.el, gomoku.el,
landmark.el et.al.
----------------------------------------------------------------

Copy the snippet below to *scratch* buffer and eval them.  (I assume
that your *scratch* buffer is in emacs-lisp-mode and is colorful)

Keep C-f-ing and C-b-ing and see what happens.

You will see that entered and left get triggered when you move from a
text that has one face to another, NOT when they have the same faces.

    (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))

----------------------------------------------------------------

Doc (makes) an (incomplete and) incorrect claim that the triggering of
hook depends SOLELY on the value of point-left and point-entered
properties.  It is NOT so.  The values of TEXT PROPERTIES should be
DIFFERENT at the transition point.





  reply	other threads:[~2013-09-10  3:33 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 [this message]
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
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=878uz573kr.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 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.