From: Eli Zaretskii <eliz@gnu.org>
To: JD Smith <jdtsmith@gmail.com>
Cc: 67604@debbugs.gnu.org
Subject: bug#67604: Motion problems with inline images
Date: Wed, 06 Dec 2023 05:31:34 +0200 [thread overview]
Message-ID: <83ttow3t2h.fsf@gnu.org> (raw)
In-Reply-To: <8698018C-6994-4CD2-8810-F77A65D60212@gmail.com> (message from JD Smith on Tue, 5 Dec 2023 18:06:41 -0500)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Tue, 5 Dec 2023 18:06:41 -0500
> Cc: 67604@debbugs.gnu.org
>
> >> Before or after the test?
> >
> > After the test.
>
> 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).
> For me both NS and Mac builds with your most recent xdisp.c fixes exhibit the same motion issue. Do you have anyone you can call in to try the simple test on another build?
Not really, no. But reproducing the problem is just a step towards
debugging it, so the alternative is for you to step through next-line
and its subroutines (or in C through vertical-motion) and tell what
happens there, and preferably also why. It isn't like I'm the only
one who should be able to read the code and understand where it fails.
next prev parent reply other threads:[~2023-12-06 3:31 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 [this message]
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
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
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=83ttow3t2h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67604@debbugs.gnu.org \
--cc=jdtsmith@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).