From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65187-done@debbugs.gnu.org, awrhygty@outlook.com
Subject: bug#65187: 29.1; right edge of wide image can not be displayed in image-mode
Date: Tue, 15 Aug 2023 01:58:12 +0200 [thread overview]
Message-ID: <87r0o5p46j.fsf@web.de> (raw)
In-Reply-To: <83msytc05z.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 14 Aug 2023 14:51:04 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> It _is_ made visible, but if the portion of the image that exceeds the
> window's width is small enough, the result is that the few extra
> pixels are clipped, but from the display engine's POV we are "at the
> right edge". IOW, the horizontal scrolling in Emacs works on the
> column granularity, not on pixel granularity.
Would it make sense to scroll one column further then? This could be
the more convenient behavior (most users know C-e better than how to
scroll horizontally, and it might be necessary to scroll further to
really see the right edge to check whether the image has a border or
something like that) and IMO would also fit the docstring a bit better.
Michael.
next prev parent reply other threads:[~2023-08-14 23:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 0:00 bug#65187: 29.1; right edge of wide image can not be displayed in image-mode awrhygty
2023-08-10 8:22 ` Eli Zaretskii
2023-08-11 0:23 ` Michael Heerdegen
2023-08-11 6:15 ` Eli Zaretskii
2023-08-11 6:29 ` Michael Heerdegen
2023-08-13 6:53 ` Eli Zaretskii
2023-08-14 0:37 ` Michael Heerdegen
2023-08-14 11:51 ` Eli Zaretskii
2023-08-14 23:58 ` Michael Heerdegen [this message]
2023-08-15 15:35 ` Eli Zaretskii
2023-08-15 3:54 ` awrhygty
2023-08-15 10:56 ` Eli Zaretskii
2023-08-15 13:03 ` awrhygty
2023-08-15 14:12 ` Eli Zaretskii
2023-08-15 14:27 ` awrhygty
2023-08-15 14:51 ` Eli Zaretskii
2023-08-15 16:35 ` Eli Zaretskii
2023-08-16 3:26 ` awrhygty
2023-08-16 17:43 ` Eli Zaretskii
2023-08-24 5:44 ` 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=87r0o5p46j.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=65187-done@debbugs.gnu.org \
--cc=awrhygty@outlook.com \
--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).