From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 20168-done@debbugs.gnu.org
Subject: bug#20168: 25.0.50; (elisp) `Accessing Mouse', for `posn-object-x-y'
Date: Mon, 23 Mar 2015 18:41:28 +0200 [thread overview]
Message-ID: <83pp7zr7if.fsf@gnu.org> (raw)
In-Reply-To: <3d0b2930-70ed-4201-a451-1813a255658b@default>
> Date: Sun, 22 Mar 2015 11:47:28 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 20168@debbugs.gnu.org
>
> > > The doc string is OK. The manual is misleading/incorrect, in this
> > > regard: it speaks about a case where "the POSITION is a buffer
> > > position". This is wrong, as a buffer position in Emacs means a natural
> > > number 1,2... (or a marker).
> >
> > Why is it wrong?
>
> It is wrong to say that the value is a buffer position, because a
> buffer position is a number, not a position object (which is a cons).
>
> > > Maybe what should be said in this case is
> > > that "POSITION represents a buffer position". Its value cannot be
> > > simply a buffer position, which is a number or a marker.
> >
> > Why not? And what's the difference between the current text and your
> > suggestion?
>
> The difference is the difference between "is" and "represents".
> The value *is* not a buffer position (which is a number). It *is*
> a position object (which is a cons). It represents a buffer position
> in this case.
>
> It's a minor point, but it was enough to confuse me into trying
> to pass an actual buffer position. Nothing in the current
> description says that POSITION must be a position object (i.e.,
> something for which `posnp' returns non-nil).
OK, fixed. Thanks.
next prev parent reply other threads:[~2015-03-23 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<11c136fa-59e2-47ed-8dac-4ce32aa91845@default>
[not found] ` <<83d240sxmo.fsf@gnu.org>
2015-03-22 18:47 ` bug#20168: 25.0.50; (elisp) `Accessing Mouse', for `posn-object-x-y' Drew Adams
2015-03-23 16:41 ` Eli Zaretskii [this message]
2015-03-22 18:14 Drew Adams
2015-03-22 18:19 ` Eli Zaretskii
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=83pp7zr7if.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20168-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).