From: Eli Zaretskii <eliz@gnu.org>
To: Rah Guzar <rahguzar@zohomail.eu>
Cc: 62679@debbugs.gnu.org, larsi@gnus.org
Subject: bug#62679: 29.0.60; Bindings on `image-map` cause error on sliced images
Date: Thu, 06 Apr 2023 19:24:18 +0300 [thread overview]
Message-ID: <83y1n5ou6l.fsf@gnu.org> (raw)
In-Reply-To: <87pm8hat4s.fsf@zohomail.eu> (message from Rah Guzar on Thu, 06 Apr 2023 17:43:55 +0200)
> From: Rah Guzar <rahguzar@zohomail.eu>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 62679@debbugs.gnu.org
> Date: Thu, 06 Apr 2023 17:43:55 +0200
>
> Hi Eli,
> I can confirm that the issue is mostly fixed now. One thing I noticed
> was that it is still possible to trigger the error by starting with my
> recipe before, moving the point to somewhere on the image and then
> using right arrow key. Since the image has a single column the point
> is now off image but on the same line. This buffer position still has
> the "image-map" and pressing e.g. "i +" still causes the error.
I cannot reproduce this. On my system, if I move point with the right
arrow key, "M-x describe-text-properties" doesn't show the keymap
property.
> According to the info manual, the advantage of using sliced images is
> to get a more intuitive scrolling behavior and that is the reason I am
> using them. I think for everything else the image should behave as a
> single image. For that reason the behavior of "i r" seems correct to
> me. It rotates the image and then slices.
If this is what you see, I guess you have Emacs built with
ImageMagick? I don't see "rotation followed by slicing", because the
code doesn't do that, at least not with rotation that is implemented
natively in Emacs on my system. But, as I said, rotation of sliced
image is not well defined, so my opinion is that people should not
depend on it doing something sensible.
next prev parent reply other threads:[~2023-04-06 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 15:23 bug#62679: 29.0.60; Bindings on `image-map` cause error on sliced images Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-06 9:41 ` Eli Zaretskii
2023-04-06 15:43 ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-06 16:24 ` Eli Zaretskii [this message]
2023-04-06 18:30 ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-08 9:46 ` Eli Zaretskii
2023-04-08 18:29 ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-08 18:58 ` 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=83y1n5ou6l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62679@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rahguzar@zohomail.eu \
/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).