From: JD Smith <jdtsmith@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67604@debbugs.gnu.org
Subject: bug#67604: Motion problems with inline images
Date: Mon, 11 Dec 2023 17:06:24 -0500 [thread overview]
Message-ID: <557B0CA0-17C4-4223-9666-4097B75BC30D@gmail.com> (raw)
In-Reply-To: <838r60v81p.fsf@gnu.org>
> On Dec 11, 2023, at 2:44 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: JD Smith <jdtsmith@gmail.com>
>> Date: Mon, 11 Dec 2023 14:06:38 -0500
>> Cc: 67604@debbugs.gnu.org
>>
>>
>>
>>> On Dec 5, 2023, at 10:31 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>>> OK, so this was likely a false positive then. I’m out of ideas. Maybe Windows is magically immune.
>>>
>>> Unlikely. More likely is that we need some specific metrics of the
>>> displayed stuff to see the problem (which is therefore very rare).
>>
>> I agree with this sentiment: it does seem to require special tuning to reveal itself. I wanted to check to see if you had received my news that I reproduced the line-skip motion bug on a GNU/Linux system. That would seem to confirm it’s a general issue with the display/motion code dealing with inline images. Let me know if I can produce anything else to help with this one. Thanks.
>
> I've eventually succeeded in reproducing it. I will get to it when I
> have time; however, with the current tempest on emacs-devel and other
> urgent issues, I don't know when will that be.
Thanks for the update, glad you could reproduce it. It will be waiting when you have a moment; hope the dust settles soon.
next prev parent reply other threads:[~2023-12-11 22:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 16:54 bug#67604: Motion problems with inline images JD Smith
2023-12-03 17:11 ` Eli Zaretskii
2023-12-03 20:46 ` JD Smith
2023-12-04 13:16 ` Eli Zaretskii
2023-12-04 14:10 ` JD Smith
2023-12-04 14:17 ` Eli Zaretskii
2023-12-04 14:25 ` JD Smith
2023-12-04 14:37 ` Eli Zaretskii
2023-12-04 17:44 ` JD Smith
2023-12-04 18:20 ` Eli Zaretskii
2023-12-04 19:16 ` JD Smith
2023-12-04 19:38 ` Eli Zaretskii
2023-12-04 21:05 ` JD Smith
2023-12-05 3:24 ` Eli Zaretskii
2023-12-05 23:06 ` JD Smith
2023-12-06 3:31 ` Eli Zaretskii
2023-12-06 4:33 ` JD Smith
2023-12-06 12:25 ` Eli Zaretskii
2023-12-06 18:29 ` JD Smith
2023-12-11 19:06 ` JD Smith
2023-12-11 19:44 ` Eli Zaretskii
2023-12-11 22:06 ` JD Smith [this message]
2024-09-03 18:00 ` JD Smith
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=557B0CA0-17C4-4223-9666-4097B75BC30D@gmail.com \
--to=jdtsmith@gmail.com \
--cc=67604@debbugs.gnu.org \
--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 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.