unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Mark Hepburn" <mark@markhepburn.com>
To: "Jim Porter" <jporterbugs@gmail.com>, "Eli Zaretskii" <eliz@gnu.org>
Cc: 72710@debbugs.gnu.org
Subject: bug#72710: 31.0.50; visual-wrap-prefix-mode freezes rendering in conjunction with diff-hl (fringe display)
Date: Sun, 25 Aug 2024 10:11:48 +1000	[thread overview]
Message-ID: <57b5c930-9ed1-4ee1-8150-35ec198ae0cd@app.fastmail.com> (raw)
In-Reply-To: <68229ac3-f783-8e8d-b3c5-0821b1d42c5e@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

Thanks Jim, that does seem to work for me.

On Sun, Aug 25, 2024, at 2:29 AM, Jim Porter wrote:
> On 8/24/2024 2:01 AM, Eli Zaretskii wrote:
> >> Date: Mon, 19 Aug 2024 22:15:51 +1000
> >> From: "Mark Hepburn" <mark@markhepburn.com>
> >>
> >> Turning on the recently-merged visual-wrap-prefix-mode while using the
> >> fringe display of diff-hl (a mode to display uncommitted file changes in
> >> the fringe area) causes rendering to completely freeze.  No backtrace is
> >> reported, although subsequent visual-line-move commands produce an
> >> error.  Emacs itself is responsive, so the file can be re-opened with
> >> `find-alternate-file'.
> [snip]
> > Jim, could you please look into this?
> 
> This sounds like bug#72721. Mark, could you try applying Eli's patch 
> here and see if it fixes the bug? 
> <https://lists.gnu.org/archive/html/bug-gnu-emacs/2024-08/msg00919.html>
> 

[-- Attachment #2: Type: text/html, Size: 1553 bytes --]

  reply	other threads:[~2024-08-25  0:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-19 12:15 bug#72710: 31.0.50; visual-wrap-prefix-mode freezes rendering in conjunction with diff-hl (fringe display) Mark Hepburn
2024-08-24  9:01 ` Eli Zaretskii
2024-08-24 16:29   ` Jim Porter
2024-08-25  0:11     ` Mark Hepburn [this message]
2024-08-25  5:53       ` 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=57b5c930-9ed1-4ee1-8150-35ec198ae0cd@app.fastmail.com \
    --to=mark@markhepburn.com \
    --cc=72710@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jporterbugs@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).