unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 72392@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#72392: 30.0.50; Wrong `next-line` behavior
Date: Fri, 02 Aug 2024 09:57:25 +0300	[thread overview]
Message-ID: <867cczwgx6.fsf@gnu.org> (raw)
In-Reply-To: <jwvcymu6my6.fsf-monnier+@gnu.org> (bug-gnu-emacs@gnu.org)

> Cc: monnier@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@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





  reply	other threads:[~2024-08-02  6:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31  7:43 bug#72392: 30.0.50; Wrong `next-line` behavior Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-02  6:57 ` Eli Zaretskii [this message]
2024-08-24  8:22   ` 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=867cczwgx6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72392@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).