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 15:16:47 +0200 [thread overview]
Message-ID: <83ttoy5cqo.fsf@gnu.org> (raw)
In-Reply-To: <190CBBD6-067F-41D8-B5EE-6E1643F01C02@gmail.com> (message from JD Smith on Sun, 3 Dec 2023 15:46:38 -0500)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Sun, 3 Dec 2023 15:46:38 -0500
> Cc: 67604@debbugs.gnu.org
>
> * Run the let-form mentioned in my initial message.
> * Resize the frame width down until the green image first moves to the beginning of a visual line (80
> chars, for me).
> * Resize down one more column *without causing further wrap* (79 chars for me).
> * In the svg-file-motion-demo buffer, execute M-x my/find-skip-bug.
> * It should report the pixel width needed for the red SVG image on the first line to trigger the bug,
> and leave the demo buffer in that state.
Instead of reporting the size, it says "Did not find Bug".
next prev parent reply other threads:[~2023-12-04 13:16 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 [this message]
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
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=83ttoy5cqo.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).