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: Sun, 03 Dec 2023 19:11:50 +0200 [thread overview]
Message-ID: <83cyvn6wix.fsf@gnu.org> (raw)
In-Reply-To: <E1F6123B-DA1E-419B-B305-43A31A5876A6@gmail.com> (message from JD Smith on Sun, 3 Dec 2023 11:54:27 -0500)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Sun, 3 Dec 2023 11:54:27 -0500
>
> Following on from the recently fixed bug#67533, which related to incorrect pixel size measurements
> with inline images, one remaining issue, with that fix in place, relates to motion in buffers in visual line
> mode with inline images. A video of the effect can be seen on the associated gist for bug#67533.
>
> Here the issue is that next-line/forward-line/(vertical-motion 1) all skip from the Green inline SVG
> straight to the “JUMPS HERE” line, for certain frame widths (for me: 79 characters). See
> reproduction code, below. Depending on your font char size (mine is 7x14 pixels) this width may
> vary for you. Note that multiple frame width produce the exact same wrapped appearance, but the
> motion bug shows up only for one of them.
I tried different frame widths, but couldn't reproduce the problem.
Not with the latest master branch, anyway, where I recently installed
the changes from bug#67533.
If someone can tell what frame width and default font height trigger
the problem, I will try to reproduce with those sizes.
next prev parent reply other threads:[~2023-12-03 17:11 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 [this message]
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
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=83cyvn6wix.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.