From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
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 13:55:28 +0800 [thread overview]
Message-ID: <87k0aw601b.fsf@yahoo.com> (raw)
In-Reply-To: <83tua0wpt7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 08 May 2022 08:34:12 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> 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?
No, I found I could reproduce it on GNU/Linux as well (with some
coaxing).
The problem is windows are not marked for redisplay after their vscroll
changes, so redisplay only happens to the selected window after just
setting the vscroll.
I suppose `wset_redisplay' would work too.
next prev parent reply other threads:[~2022-05-08 5:55 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
2022-05-08 5:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87k0aw601b.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=55299@debbugs.gnu.org \
--cc=eliz@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).