From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: 57433@debbugs.gnu.org
Subject: bug#57433: Emacs no longer moves point into visible port of the buffer
Date: Sat, 27 Aug 2022 08:55:49 +0200 [thread overview]
Message-ID: <m2edx218ga.fsf@Mini.fritz.box> (raw)
In-Reply-To: <CAG7BpapeVEoEOV1A5+RNGoviMrFmOHp1gRPV4FO=DTo363dv6A@mail.gmail.com> (Paul Pogonyshev's message of "Fri, 26 Aug 2022 18:32:14 +0200")
Paul Pogonyshev <pogonyshev@gmail.com> writes:
> Git commit 233c91d32a. Has been broken at least for a few days: my previous build also exhibited this.
>
> No idea how to create a short test in Elisp.
>
> From user point of view: open a Magit buffer in a directory with at least two locally modified and uncommitted files. The buffer shows sth. like
> this:
>
> ...
> Staged changes (N)
> modified file1
> modified file2
> ...
>
> Move the point with C-n to the line with `file2'. Press TAB. Magit section for the file is not opened. Use `M-x describe-char'. From the resulting
> buffer you can say that the point is actually on an invisible char '@', i.e. start of (hidden) diff for the first file.
>
> It may be necessary to restart Emacs if you have used Magit in this directory previously.
>
> This used to work fine (i.e. point was never on an invisible character) both in Emacs 28 and earlier snapshots of `master'.
>
> Paul
I can reproduce this. Bisecting.
next prev parent reply other threads:[~2022-08-27 6:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 16:32 bug#57433: Emacs no longer moves point into visible port of the buffer Paul Pogonyshev
2022-08-27 6:55 ` Gerd Möllmann [this message]
2022-08-27 8:08 ` Gerd Möllmann
2022-08-27 8:53 ` Gerd Möllmann
2022-08-27 9:33 ` Eli Zaretskii
2022-08-27 9:55 ` Gerd Möllmann
2022-08-27 9:58 ` Eli Zaretskii
2022-08-27 10:02 ` Gerd Möllmann
2022-08-27 10:19 ` Eli Zaretskii
2022-08-27 10:43 ` Gerd Möllmann
2022-08-27 11:08 ` Eli Zaretskii
2022-08-27 14:07 ` Paul Pogonyshev
2022-08-27 14:28 ` Gerd Möllmann
2022-08-27 15:47 ` Paul Pogonyshev
2022-08-27 15:55 ` Eli Zaretskii
2022-08-27 16:06 ` Paul Pogonyshev
2022-08-27 16:12 ` Paul Pogonyshev
2022-08-27 16:29 ` Eli Zaretskii
2022-08-27 16:32 ` Paul Pogonyshev
2022-08-27 16:37 ` Paul Pogonyshev
2022-08-27 16:56 ` Eli Zaretskii
2022-08-27 17:01 ` Paul Pogonyshev
2022-08-27 17:11 ` Paul Pogonyshev
2022-08-27 16:25 ` Eli Zaretskii
2022-08-27 15:13 ` Eli Zaretskii
2022-08-27 9:47 ` 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=m2edx218ga.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=57433@debbugs.gnu.org \
--cc=pogonyshev@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).