From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 57433@debbugs.gnu.org, pogonyshev@gmail.com
Subject: bug#57433: Emacs no longer moves point into visible port of the buffer
Date: Sat, 27 Aug 2022 13:19:20 +0300 [thread overview]
Message-ID: <83sfliyonr.fsf@gnu.org> (raw)
In-Reply-To: <m25yierolj.fsf@Mini.fritz.box> (message from Gerd Möllmann on Sat, 27 Aug 2022 12:02:32 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: 57433@debbugs.gnu.org, pogonyshev@gmail.com
> Date: Sat, 27 Aug 2022 12:02:32 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Does Magit turn on truncate-lines in the affected buffer, or cause
> > them be truncated due to partial-width windows? If it does, I might
> > have an idea what could cause the OP's problem.
>
> Yes, truncate-lines it t.
In that case, can you see if the patch below solves the original issue
with Magit?
diff --git a/lisp/simple.el b/lisp/simple.el
index ee765c8..d18d54c 100644
--- a/lisp/simple.el
+++ b/lisp/simple.el
@@ -7717,13 +7717,15 @@ line-move
(not goal-column)
;; Lines aren't truncated.
(not
- (or truncate-lines
- (and (integerp truncate-partial-width-windows)
- (< (window-width)
- truncate-partial-width-windows))
- (and truncate-partial-width-windows
- (not (integerp truncate-partial-width-windows))
- (not (window-full-width-p)))))
+ (and
+ (or truncate-lines
+ (and (integerp truncate-partial-width-windows)
+ (< (window-total-width)
+ truncate-partial-width-windows))
+ (and truncate-partial-width-windows
+ (not (integerp truncate-partial-width-windows))
+ (not (window-full-width-p))))
+ (long-line-optimizations-p)))
;; When the text in the window is scrolled to the left,
;; display-based motion doesn't make sense (because each
;; logical line occupies exactly one screen line).
next prev parent reply other threads:[~2022-08-27 10:19 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sfliyonr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57433@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.