From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46552@debbugs.gnu.org, ynyaaa@gmail.com
Subject: bug#46552: 27.1; image-mode should not move current point
Date: Tue, 16 Feb 2021 19:53:18 +0200 [thread overview]
Message-ID: <83mtw399wx.fsf@gnu.org> (raw)
In-Reply-To: <875z2rvrjf.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 16 Feb 2021 18:41:40 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: ynyaaa@gmail.com, 46552@debbugs.gnu.org
> Date: Tue, 16 Feb 2021 18:41:40 +0100
>
> > IOW, from the user's POV, the image is a single "cell" on display, so
> > any forward movement of point ends up _after_ the image, where the
> > commands like '+' aren't supposed to work.
>
> I think that sounds quite surprising. There's nothing much to do in an
> image-mode buffer than interact with the image, and this makes
> interaction not work.
But so does "C-c C-c". "If it hurts, don't do that."
More importantly, I think disabling the point adjustments will cause
very surprising behavior: it allows moving point many times (as many
as there are bytes in the image file) without any visible effect.
That's something we want very much to avoid, and it is the main reason
why we have this point-adjustment feature. Disabling it is a
debugging tool, not something to show to users.
next prev parent reply other threads:[~2021-02-16 17:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 9:21 bug#46552: 27.1; image-mode should not move current point ynyaaa
2021-02-16 12:36 ` Lars Ingebrigtsen
2021-02-16 16:32 ` Eli Zaretskii
2021-02-16 16:40 ` Lars Ingebrigtsen
2021-02-16 16:43 ` Lars Ingebrigtsen
2021-02-16 17:04 ` Eli Zaretskii
2021-02-16 17:09 ` Lars Ingebrigtsen
2021-02-16 17:39 ` Eli Zaretskii
2021-02-16 17:41 ` Lars Ingebrigtsen
2021-02-16 17:53 ` Eli Zaretskii [this message]
2021-02-16 21:46 ` Lars Ingebrigtsen
2021-02-16 17:57 ` Eli Zaretskii
2021-02-16 18:10 ` Lars Ingebrigtsen
2021-02-16 17:17 ` Juri Linkov
2021-02-16 16:24 ` 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=83mtw399wx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46552@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=ynyaaa@gmail.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).