From: Po Lu <luangruo@yahoo.com>
To: "Arsen Arsenović" <arsen@aarsen.me>
Cc: Eli Zaretskii <eliz@gnu.org>, Ergus <spacibba@aol.com>,
gerd.moellmann@gmail.com, avityazev@disroot.org,
emacs-devel@gnu.org, eller.helmut@gmail.com
Subject: Re: MPS and pgtk
Date: Thu, 27 Jun 2024 20:26:20 +0800 [thread overview]
Message-ID: <87wmmatvv7.fsf@yahoo.com> (raw)
In-Reply-To: <86jziapu1b.fsf@aarsen.me> ("Arsen Arsenović"'s message of "Thu, 27 Jun 2024 12:19:28 +0200")
Arsen Arsenović <arsen@aarsen.me> writes:
> I am curious about what these are, as I am quite interested in the
> further development of Wayland. IMO, X has overstayed its welcome, as
> it is flawed from the ground up, visibly (to the point where I was quite
> surprised the other day when I opened an X session to find noticeable
> issues handling mixed refresh rate, and flickering when windows were
> changing sizes or opening/closing).
At fault is probably your X compositing manager or poor engineering in
he client, not the X server, and least of all the extensible X
protocol...
> I am aware of the GTK issues of not being able to multihead or handle
> disconnects, but the only Wayland one I am aware of is lack of a way to
> know which frames are visible (which I don't see as a big issue.. and it
> is perhaps fixable anyway).
If Emacs is to be satisfactory citizen of the Wayland desktop,
facilities for moving frames on the virtual desktop and reading their
positions are a non-negotiable must. It's really too bad that this is
literally anathema to Wayland's designers as one of the putative
misdesigns of X they chose to target for eradication. This of all
things!
Gracefully responding to disconnects, and suchlike, are deficiencies in
GTK that will be addressed if and when I determine to commit myself to
implementing a Wayland terminal backend independent of all but the
Wayland client libraries and protocol definitions, though, needless to
say, no tears will be shed if anyone will undertake this now.
> WRT GTK, I've considered Qt (but have not seen yet whether it has the
> same restrictions) and multiprocessing the UI, but have not had time to
> look into those options yet. Has anyone lese considered Qt?
Qt is equally incapable of responding to interruptions to display
connections, AFAIK.
next prev parent reply other threads:[~2024-06-27 12:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 12:56 MPS and pgtk Aleksandr Vityazev
2024-06-26 16:38 ` Gerd Möllmann
2024-06-26 22:38 ` Ergus
2024-06-27 0:26 ` Fejfighter
2024-06-27 3:59 ` Gerd Möllmann
2024-06-27 6:12 ` Eli Zaretskii
2024-06-27 19:07 ` Helmut Eller
2024-06-27 19:23 ` Gerd Möllmann
2024-06-28 3:13 ` Gerd Möllmann
2024-06-27 3:57 ` Gerd Möllmann
2024-06-27 6:08 ` Eli Zaretskii
2024-06-27 5:40 ` Eli Zaretskii
2024-06-27 6:09 ` Po Lu
2024-06-27 10:19 ` Arsen Arsenović
2024-06-27 10:36 ` Eli Zaretskii
2024-07-06 0:32 ` Konstantin Kharlamov
2024-06-27 12:26 ` Po Lu [this message]
2024-07-05 21:41 ` Björn Bidar
[not found] ` <871q47freu.fsf@>
2024-07-06 2:01 ` Daniel Colascione
2024-07-07 3:11 ` Richard Stallman
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=87wmmatvv7.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=arsen@aarsen.me \
--cc=avityazev@disroot.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=spacibba@aol.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).