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, 4 Dec 2023 16:05:56 -0500 [thread overview]
Message-ID: <E5EDCDA9-8EF3-40A1-810D-B8B04B22E5EA@gmail.com> (raw)
In-Reply-To: <83jzpt69my.fsf@gnu.org>
> On Dec 4, 2023, at 2:38 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: JD Smith <jdtsmith@gmail.com>
>> Date: Mon, 4 Dec 2023 14:16:10 -0500
>> Cc: 67604@debbugs.gnu.org
>>
>>> 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.
>>
>>
>> OK great. Is it possible at offset = -6 = 140 pixels the green image has wrapped back onto line 1? That’s a “false positive” bug. The layout after my/find-skip-bug has found the magic width must look as in my prior screenshot (with green image at the beginning of screen line 2) or it’s not a real bug.
>
> No, it looks with the green image at the visual end of a screen line.
Before or after the test? If before the test, you haven’t tried this, please resize the frame until the green image wraps to visual line 2, then reduce width by one column more.
next prev parent reply other threads:[~2023-12-04 21:05 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
2023-12-04 19:16 ` JD Smith
2023-12-04 19:38 ` Eli Zaretskii
2023-12-04 21:05 ` JD Smith [this message]
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=E5EDCDA9-8EF3-40A1-810D-B8B04B22E5EA@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.