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: 72681-done@debbugs.gnu.org
Subject: bug#72681: 31.0.50; visual-wrap-prefix-mode interacts badly with plain lists in org-mode
Date: Sun, 18 Aug 2024 19:53:36 +1000	[thread overview]
Message-ID: <10e7d27d-0891-4e7c-a42a-ddc448ad91f7@app.fastmail.com> (raw)
In-Reply-To: <7342c229-29c3-055c-e453-3f661197f441@gmail.com>

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

Hi again Jim,

I haven't isolated this one yet, but I'm flagging in case it rings any bells for you -- I'm getting rendering-lockups with dart-mode when I enable visual-wrap-prefix-mode.  I've checked a couple of other programming modes which seem fine.  My money was on lsp-mode (and maybe lens display), but I've disabled lsp entirely and it still locks up.

I don't get a backtrace (with debug-on-error), but I can get this (when I hit C-n to see anything is happening, as the screen goes blank):
===
Debugger entered--Lisp error: (args-out-of-range 519 519)
  line-move-visual(1 nil)
  line-move(1 nil nil 1)
  next-line(1 1)
  funcall-interactively(next-line 1 1)
  command-execute(next-line)
===

I'll keep trying to isolate it.  So far my repo is "open .dart file, M-x visual-wrap-prefix-mode".

cheers, Mark

On Sun, Aug 18, 2024, at 11:40 AM, Jim Porter wrote:
> On 8/17/2024 5:02 PM, Mark Hepburn wrote:
> > Thanks Jim, nice work -- yes that seems to work perfectly again for all 
> > the problematic files I had before.
> 
> Great, thanks for checking. I've therefore merged this to the master 
> branch as 135da3556bb. Closing this bug now.
> 
> (Though of course if you find any other issues with the new 
> 'visual-wrap-prefix-mode' code, just let me know and I'll try to fix it.)
> 

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

  reply	other threads:[~2024-08-18  9:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17  2:21 bug#72681: 31.0.50; visual-wrap-prefix-mode interacts badly with plain lists in org-mode Mark Hepburn
2024-08-17  7:19 ` Eli Zaretskii
2024-08-17 20:29   ` Jim Porter
2024-08-18  0:02     ` Mark Hepburn
2024-08-18  1:40       ` Jim Porter
2024-08-18  9:53         ` Mark Hepburn [this message]
2024-08-18 17:11           ` Jim Porter
     [not found]             ` <a552da1e-80b9-42f1-900c-2255c65a63d4@app.fastmail.com>
     [not found]               ` <CANh=_JH9GcCGhuLQUZeGZ89CnpYTuWmEGwKXRQ=zY-7X4WzUmg@mail.gmail.com>
     [not found]                 ` <31873240-cedb-4a6e-825c-2ad60caa8b11@app.fastmail.com>
     [not found]                   ` <3cbd38fd-82e5-46aa-bc51-a8cd3caf688d@app.fastmail.com>
2024-08-25  5:55                     ` Eli Zaretskii
2024-08-25 18:50                       ` Jim Porter
2024-08-25 20:58                         ` Mark Hepburn

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=10e7d27d-0891-4e7c-a42a-ddc448ad91f7@app.fastmail.com \
    --to=mark@markhepburn.com \
    --cc=72681-done@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).