GNU bug report logs - #20168
25.0.50; (elisp) `Accessing Mouse', for `posn-object-x-y'

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Sun, 22 Mar 2015 18:15:02 UTC

Severity: wishlist

Found in version 25.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 20168 in the body.
You can then email your comments to 20168 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#20168; Package emacs. (Sun, 22 Mar 2015 18:15:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Drew Adams <drew.adams <at> oracle.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sun, 22 Mar 2015 18:15:03 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.0.50; (elisp) `Accessing Mouse', for `posn-object-x-y'
Date: Sun, 22 Mar 2015 11:14:28 -0700 (PDT)
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).  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.

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2014-10-20 on LEG570
Bzr revision: 118168 rgm <at> gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#20168; Package emacs. (Sun, 22 Mar 2015 18:21:01 GMT) Full text and rfc822 format available.

Message #8 received at 20168 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 20168 <at> debbugs.gnu.org
Subject: Re: bug#20168: 25.0.50;
 (elisp) `Accessing Mouse', for `posn-object-x-y'
Date: Sun, 22 Mar 2015 20:19:43 +0200
> Date: Sun, 22 Mar 2015 11:14:28 -0700 (PDT)
> From: Drew Adams <drew.adams <at> oracle.com>
> 
> 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?

> 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?

Or maybe you could provide an example where the docs are wrong.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#20168; Package emacs. (Sun, 22 Mar 2015 18:48:01 GMT) Full text and rfc822 format available.

Message #11 received at 20168 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 20168 <at> debbugs.gnu.org
Subject: RE: bug#20168: 25.0.50; (elisp) `Accessing Mouse', for
 `posn-object-x-y'
Date: Sun, 22 Mar 2015 11:47:28 -0700 (PDT)
> > 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).




Reply sent to Eli Zaretskii <eliz <at> gnu.org>:
You have taken responsibility. (Mon, 23 Mar 2015 16:42:02 GMT) Full text and rfc822 format available.

Notification sent to Drew Adams <drew.adams <at> oracle.com>:
bug acknowledged by developer. (Mon, 23 Mar 2015 16:42:02 GMT) Full text and rfc822 format available.

Message #16 received at 20168-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 20168-done <at> debbugs.gnu.org
Subject: Re: bug#20168: 25.0.50;
 (elisp) `Accessing Mouse', for `posn-object-x-y'
Date: Mon, 23 Mar 2015 18:41:28 +0200
> Date: Sun, 22 Mar 2015 11:47:28 -0700 (PDT)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: 20168 <at> 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.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Tue, 21 Apr 2015 11:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 10 years and 62 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.