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: Mon, 04 Dec 2023 20:20:40 +0200 [thread overview]
Message-ID: <83lea96d8n.fsf@gnu.org> (raw)
In-Reply-To: <9F116A2F-AC1C-4E7D-8870-60561BFD537C@gmail.com> (message from JD Smith on Mon, 4 Dec 2023 12:44:45 -0500)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Mon, 4 Dec 2023 12:44:45 -0500
> Cc: 67604@debbugs.gnu.org
>
> Wonders never cease. I just picked an 8x16 font and it worked fine, finding the bug at offset=2 (i.e. red svg=148 pixels wide). This was using the build from this morning with your recent xdisp.c fix. To be sure we’re on the same page, I’ve included again the test code below.
Now I run it and I get
Found Bug at offset -6 = 140 pixels
but the problem with cursor jumping to "JUMPS HERE" still doesn't
happen.
> One other scraping-the-barrel's-bottom idea: I’ve found before that (frame-char-width) when called “too early” yields incorrect/missing results; are you running the code interactively, or via a batch style setup? Do you see a nice range of “Check with red image width …” messages?
I'm running the code interactively, and I do see those "Check..."
messages (mainly in *Messages*, as they are very quickly replaced by
the finishing message).
next prev parent reply other threads:[~2023-12-04 18:20 UTC|newest]
Thread overview: 22+ 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 [this message]
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
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=83lea96d8n.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 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.