GNU bug report logs - #72392
30.0.50; Wrong `next-line` behavior

Previous Next

Full log

Message #11 received at 72392 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: monnier <at> iro.umontreal.ca
Cc: 72392 <at> debbugs.gnu.org
Subject: Re: bug#72392: 30.0.50; Wrong `next-line` behavior
Date: Sat, 24 Aug 2024 11:22:08 +0300

Ping! A simple test case could go a long way towards a solution.

> Cc: 72392 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca
> Date: Fri, 02 Aug 2024 09:57:25 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > Cc: monnier <at> iro.umontreal.ca
> > Date: Wed, 31 Jul 2024 03:43:20 -0400
> > From:  Stefan Monnier via "Bug reports for GNU Emacs,
> >  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> > 
> > - Apply the `smerge-mode.patch` below to Emacs's` master` (and
> >   recompile `smerge-mode.el`).
> > - Open the short diff file below with:
> > 
> >     emacs -Q --eval '(setq-default word-wrap t diff-font-lock-prettify t)' \
> >           .../bug-weird-next-line.diff
> > 
> > - In my case, when this opens there's a "word wrap" just before "This"
> >   and just before "\id{seg}" (on the 4th and 5th lines, resp).
> >   If that's not the case for you, resize your frame so that this is
> >   the case.
> > 
> > - Do `C-n` a few times.
> 
> Any hope of a simpler recipe, which would not require patching Emacs?
> Cannot you just post the contents of the problematic buffer and the
> non-default settings to use to reproduce the problem?
> 
> The bug is probably somewhere in vertical-motion or in line-move and
> its subroutines, but a simpler recipe will make the investigation less
> painful.
> 
> TIA
> 
> 
> 
> 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.