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: Jarno Malmari <jmalmari@ftml.net>, 71591@debbugs.gnu.org
Subject: bug#71591: 30.0.50; PGTK: Terrible input lag with display scaling
Date: Thu, 27 Jun 2024 18:56:32 +0800 [thread overview]
Message-ID: <871q4ivelb.fsf@yahoo.com> (raw)
In-Reply-To: <86zfr66dc0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 27 Jun 2024 10:42:55 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Jarno Malmari <jmalmari@ftml.net>
>> Date: Sun, 16 Jun 2024 15:26:13 +0300
>>
>> With a 4k display and 150 % display scaling there is a noticeable input
>> lag when moving the point around in fullscreen. Very sluggish
>> feel. Shrinking the window helps.
>>
>> Besides "sluggish feel" I couldn't figure out easily measurable metric
>> for this. One way is to clock how long it takes to use your keyboard
>> repeat with `next-line' to reach the end of a couple pages long buffer.
>>
>> This was tested with PGTK build on KDE Plasma 6 running Wayland. X build
>> running in XWayland does not have this problem even if configured to be
>> "Scaled by the system" from the system display configuration UI.
>>
>> The scale option that affects this can also be changed with these commands:
>>
>> kscreen-doctor output.${OUTPUT_NAME}.scale.1.5
>> kscreen-doctor output.${OUTPUT_NAME}.scale.1.0
>>
>> Applies also to emacs 29.
>
> Po Lu, any suggestions or ideas?
Jarno, does your system use NVIDIA graphics drivers?
next prev parent reply other threads:[~2024-06-27 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 12:26 bug#71591: 30.0.50; PGTK: Terrible input lag with display scaling Jarno Malmari
2024-06-27 7:42 ` Eli Zaretskii
2024-06-27 10:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-27 16:12 ` Jarno Malmari
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=871q4ivelb.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=71591@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jmalmari@ftml.net \
--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).