From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 20169@debbugs.gnu.org
Subject: bug#20169: 25.0.50; doc of `posn-actual-col-row'
Date: Sun, 22 Mar 2015 12:51:17 -0700 (PDT) [thread overview]
Message-ID: <5b520826-b1f7-4725-be30-8566a9599f72@default> (raw)
In-Reply-To: <<83a8z4sw89.fsf@gnu.org>>
> > Please add the information that is in the doc string to (elisp)
> > `Accessing Mouse'. This means both the reference information about what
> > happens if POSITION does not contain the actual position and the guide
> > information about using `posn-col-row' in that case.
>
> The first part is already there, isn't it?
Do you mean this?
The function returns `nil' if POSITION does not include actual
position values.
I meant that the manual should include the information that is in
the last two paragraphs of the doc string:
Return nil if POSITION does not contain the actual position;
in that case `posn-col-row' can be used to get approximate values.
POSITION should be a list of the form returned by the `event-start'
and `event-end' functions.
This function does not account for the width on display, like the
number of visual columns taken by a TAB or image. If you need
the coordinates of POSITION in character units, you should use
`posn-col-row', not this function.
This is a lot more (and more useful) information than just what
is in its first line:
Return nil if POSITION does not contain the actual position;
next parent reply other threads:[~2015-03-22 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<33a115b6-7d7f-4a2b-a0a2-7c4de0522f0a@default>
[not found] ` <<83a8z4sw89.fsf@gnu.org>
2015-03-22 19:51 ` Drew Adams [this message]
2015-03-23 16:36 ` bug#20169: 25.0.50; doc of `posn-actual-col-row' Eli Zaretskii
2015-03-22 18:38 Drew Adams
2015-03-22 18:49 ` 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=5b520826-b1f7-4725-be30-8566a9599f72@default \
--to=drew.adams@oracle.com \
--cc=20169@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).