unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, gautier@gautierponsinet.xyz
Cc: 73600@debbugs.gnu.org
Subject: bug#73600: 31.0.50; Visual wrap prefix mode and image display
Date: Wed, 2 Oct 2024 09:37:48 -0700	[thread overview]
Message-ID: <3117d4b7-751c-8c6d-8acf-48dc6464e723@gmail.com> (raw)
In-Reply-To: <86bk021p1k.fsf@gnu.org>

On 10/2/2024 8:51 AM, Eli Zaretskii wrote:
>> Cc: 73600@debbugs.gnu.org
>> Date: Wed, 02 Oct 2024 18:42:09 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>>
>>> In emacs -Q:
>>> - enable global-visual-wrap-prefix-mode,
>>> - open the attached image.
>>
>> In a build with --enable-checking, this recipe causes an assertion
>> violation:
> 
> And in Emacs 30 the problem doesn't happen, so this is some regression
> in Emacs 31.  Probably due to my changes in commit 71505b723c9f.
> 
> Jim, any ideas or suggestions?

Strangely, this doesn't seem to happen with every image. "splash.png" in 
the Emacs repository seems fine, for example. I also can't reproduce 
this in EWW, even by opening the bad image reported in this bug.

I haven't looked into the internals of 'image-mode' very much, but I 
seem to recall that it has some special code for scrolling large images. 
Maybe that's interacting in some bad way with 'visual-wrap-prefix-mode'?

One option might simply be to disable 'visual-wrap-prefix-mode' when in 
'image-mode'. I don't think wrapping is useful in that context.





  reply	other threads:[~2024-10-02 16:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 13:04 bug#73600: 31.0.50; Visual wrap prefix mode and image display Gautier Ponsinet
2024-10-02 15:42 ` Eli Zaretskii
2024-10-02 15:51   ` Eli Zaretskii
2024-10-02 16:37     ` Jim Porter [this message]
2024-10-03 10:59       ` Eli Zaretskii
2024-10-04  0:28         ` Jim Porter
2024-10-04  6:28           ` Eli Zaretskii
2024-10-04 19:45             ` Jim Porter
2024-10-05  6:41               ` Eli Zaretskii
2024-10-05 18:07                 ` Jim Porter
2024-10-06  0:28                   ` Jim Porter
2024-10-12 12:00                   ` Eli Zaretskii
2024-10-13  1:36                     ` Jim Porter
2024-10-13  5:36                       ` Eli Zaretskii
2024-10-13 17:38                         ` Jim Porter
2024-10-13 18:51                           ` Eli Zaretskii
2024-10-13 20:50                             ` Jim Porter
2024-10-19  8:23                               ` Eli Zaretskii

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=3117d4b7-751c-8c6d-8acf-48dc6464e723@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=73600@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gautier@gautierponsinet.xyz \
    /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).