From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Politz <politza@hochschule-trier.de>
Cc: 24804@debbugs.gnu.org
Subject: bug#24804: 25.1; posn-at-point erroneously signals an error
Date: Sat, 29 Oct 2016 17:36:22 +0300 [thread overview]
Message-ID: <83funfql21.fsf@gnu.org> (raw)
In-Reply-To: <87r36zz0wo.fsf@hochschule-trier.de> (message from Andreas Politz on Sat, 29 Oct 2016 16:26:47 +0200)
> From: Andreas Politz <politza@hochschule-trier.de>
> Cc: rudalics@gmx.at, 24804@debbugs.gnu.org
> Date: Sat, 29 Oct 2016 16:26:47 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Andreas, can you try the patch below? Thanks.
>
> I can confirm, that the error regarding above recpie goes away.
Great, I will push it to master soon.
> Though I'm pretty confused about what this function should actually
> return in this case. E.g. in the scenario above, evaluating (posn-x-y
> (posn-at-point x)) with x=point-min, resp. x=point-max, returns (0 . 0),
> resp. (747 . 0), where 747 is the width of the image. Does that sound
> right ?
It sounds right to me: the first position is at the image, the second
is after the image, so its X coordinate should be the image width.
Does that make sense?
next prev parent reply other threads:[~2016-10-29 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 19:43 bug#24804: 25.1; posn-at-point erroneously signals an error Andreas Politz
[not found] ` <handler.24804.B.147751104225420.ack@debbugs.gnu.org>
2016-10-26 19:49 ` bug#24804: Acknowledgement (25.1; posn-at-point erroneously signals an error) Andreas Politz
2016-10-27 17:35 ` bug#24804: 25.1; posn-at-point erroneously signals an error martin rudalics
2016-10-27 18:26 ` Andreas Politz
2016-10-28 8:12 ` Eli Zaretskii
2016-10-29 10:23 ` Eli Zaretskii
2016-10-29 14:26 ` Andreas Politz
2016-10-29 14:36 ` Eli Zaretskii [this message]
2016-10-29 14:42 ` Eli Zaretskii
2016-10-29 20:33 ` Andreas Politz
2016-10-29 22:03 ` 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=83funfql21.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24804@debbugs.gnu.org \
--cc=politza@hochschule-trier.de \
/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).