From: awrhygty@outlook.com
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, 65187@debbugs.gnu.org
Subject: bug#65187: 29.1; right edge of wide image can not be displayed in image-mode
Date: Tue, 15 Aug 2023 22:03:53 +0900 [thread overview]
Message-ID: <TYZPR01MB3920ADABB4C43A4C49E0E0B7C314A@TYZPR01MB3920.apcprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <83y1ica80u.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 15 Aug 2023 06:56:31 -0400")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: awrhygty@outlook.com
>> Cc: michael_heerdegen@web.de, 65187@debbugs.gnu.org
>> Date: Tue, 15 Aug 2023 12:54:57 +0900
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> Cc: 65187@debbugs.gnu.org, awrhygty@outlook.com
>> >> Date: Fri, 11 Aug 2023 09:15:46 +0300
>> >> From: Eli Zaretskii <eliz@gnu.org>
>> >>
>> >> But maybe there's some fine dependency on the frame geometry here; I
>> >> will take a closer look. What bothers me is that the original recipe
>> >> signals an error, so I'm unsure what kind of code the OP ran to see
>> >> the problem to begin with.
>> >
>> > OK, I see the behavior described in the OP now.
>> >
>> > But I don't understand why is this behavior interpreted as a bug. If
>> > I type <RIGHT> arrow or C-f enough times, I eventually do see the red
>> > line on the right edge of the rectangle. So this is just the normal
>> > horizontal scrolling of images plus automatic clipping of images in
>> > action.
>> >
>> > I see no bug here. What am I missing?
>>
>> I can not view the right red line with typing many 'C-f's or 'C-e C-f'.
>
> You can enlarge the window's width instead, if you must see the last
> few pixels.
I can not if the image is much larger than display.
next prev parent reply other threads:[~2023-08-15 13:03 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=TYZPR01MB3920ADABB4C43A4C49E0E0B7C314A@TYZPR01MB3920.apcprd01.prod.exchangelabs.com \
--to=awrhygty@outlook.com \
--cc=65187@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.