From: Ruijie Yu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "J. Scott Berg" <jsberg-bnl@outlook.com>
Cc: 61258@debbugs.gnu.org
Subject: bug#61258: 29.0.60; pgtk build from git, WSLg, slow, heavy cpu use
Date: Sat, 4 Feb 2023 08:48:00 +0800 [thread overview]
Message-ID: <F702331D-30E1-411A-A86C-12B86B87CFAC@netyu.xyz> (raw)
In-Reply-To: <PH8PR14MB6016E602FE2BE968DFDB8D4E9AD79@PH8PR14MB6016.namprd14.prod.outlook.com>
On Feb 4, 2023, at 02:53, J. Scott Berg <jsberg-bnl@outlook.com> wrote:
>
> Emacs built with pgtk. Editing in f90 mode, though I don't think this is
> important. Display is WSLg. Severe input lag, to the point off becoming
> unusable, gets worse with more frames (or just time?). Heavy CPU usage by
> emacs while doing anything. Problem not seen when not built with pgtk.
Hello,
Last time I checked, PGTK only aims to support Wayland -- while incidentally also *usually but not always* work in X -- and WSLg is an X server/client thing. There is even a warning shown when I run my PGTK build on an X DE. So, intuitively, if my information is correct and up to date, you are not expected to run PGTK build on WSLg and you would need to disable the PGTK flag during config.
> In GNU Emacs 29.0.60 (build 1, x86_64-pc-linux-gnu, GTK+ Version
> 3.24.36, cairo version 1.17.6) of 2023-02-01 built on LAD-158343
> Repository revision: f91bf9df892417a2e4add6d0d77ac5123a579bfc
> Repository branch: emacs-29
> System Description: Arch Linux
>
> Configured using:
> 'configure --prefix=/home/jsberg/opt/emacs-230201-f91bf9df892
> --with-pgtk --with-native-compilation'
>
> Configured features:
> ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG
> JSON LCMS2 LIBOTF LIBSYSTEMD LIBXML2 MODULES NATIVE_COMP NOTIFY INOTIFY
> PDUMPER PGTK PNG RSVG SECCOMP SOUND SQLITE3 THREADS TIFF
> TOOLKIT_SCROLL_BARS WEBP XIM GTK3 ZLIB
Best,
RY
next prev parent reply other threads:[~2023-02-04 0:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 18:47 bug#61258: 29.0.60; pgtk build from git, WSLg, slow, heavy cpu use J. Scott Berg
2023-02-04 0:48 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-06 11:51 ` J. Scott Berg
2023-02-04 8:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-01 22:01 ` Fujii Hironori
2023-08-02 0:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-02 11:49 ` Eli Zaretskii
2023-08-02 13:00 ` J. Scott Berg
2023-08-03 1:00 ` Fujii Hironori
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=F702331D-30E1-411A-A86C-12B86B87CFAC@netyu.xyz \
--to=bug-gnu-emacs@gnu.org \
--cc=61258@debbugs.gnu.org \
--cc=jsberg-bnl@outlook.com \
--cc=ruijie@netyu.xyz \
/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).