From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 55299@debbugs.gnu.org, konrad.podczeck@univie.ac.at
Subject: bug#55299: 29.0.50; Bug with the mode-line and pixel-scroll-precision-mode
Date: Sun, 08 May 2022 08:34:12 +0300 [thread overview]
Message-ID: <83tua0wpt7.fsf@gnu.org> (raw)
In-Reply-To: <87sfpk6dn7.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)
> Cc: 55299@debbugs.gnu.org
> Date: Sun, 08 May 2022 09:01:32 +0800
> From: Po Lu via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Konrad Podczeck <konrad.podczeck@univie.ac.at> writes:
>
> > With this patch, I don’t get any error message, but If a frame has
> > only one window, I cannot scroll (using the mouse wheel) downwards
> > anymore, and after doing C-x 2, the same is true if I scroll in the
> > active pane, while when I scroll in the inactive pane, I always get
> > scrolling upwards, regardless of which direction I rotate the wheel.
>
> Does this fix your problem?
>
> diff --git a/src/window.c b/src/window.c
> index 15d6cf94b0..1e719c2598 100644
> --- a/src/window.c
> +++ b/src/window.c
> @@ -7980,6 +7980,8 @@ DEFUN ("set-window-vscroll", Fset_window_vscroll, Sset_window_vscroll,
>
> /* Prevent redisplay shortcuts. */
> XBUFFER (w->contents)->prevent_redisplay_optimizations_p = true;
> +
> + windows_or_buffers_changed = 1013;
I'm not surer we want this. It will slow down redisplay, so we need a
good understanding why this is required. And the problem happens only
on macOS, isn't that so?
next prev parent reply other threads:[~2022-05-08 5:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 9:54 bug#55299: 29.0.50; Bug with the mode-line and pixel-scroll-precision-mode Konrad Podczeck
2022-05-07 10:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 11:14 ` Konrad Podczeck
2022-05-07 11:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 13:06 ` Konrad Podczeck
2022-05-07 13:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-07 14:40 ` Konrad Podczeck
2022-05-08 0:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-08 1:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-08 5:34 ` Eli Zaretskii [this message]
2022-05-08 5:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-08 6:13 ` Eli Zaretskii
2022-05-08 7:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-08 10:01 ` Konrad Podczeck
2022-05-08 11:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-19 12:50 ` Konrad Podczeck
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=83tua0wpt7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55299@debbugs.gnu.org \
--cc=konrad.podczeck@univie.ac.at \
--cc=luangruo@yahoo.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).