all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 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 14:09:10 +0800	[thread overview]
Message-ID: <87ed8ivrw9.fsf@yahoo.com> (raw)
In-Reply-To: <86h6df6izq.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 27 Jun 2024 08:40:41 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Which is bothersome, at least from the Emacs POV, since Wayland and
> PGTK have so many limitations, restrictions, and misfeatures which
> effectively disable useful Emacs features.
>
>> So, IMHO the pgtk support may be prioritized as it is the only way we
>> support Wayland natively.
>> 
>> Not sure if there are plans or alternatives under consideration to
>> change/improve pgtk, but if igc becomes an issue for it... we may
>> rethink if we really want it looking to the future?
>
> Given the sorry state of Wayland and GTK support of what Emacs needs,
> from my POV the PGTK configuration becomes less and less relevant to
> Emacs.  I'm aware that the world moves in the opposite direction, but
> unless we get some help from Wayland/GTK developers, or,
> alternatively, find ways to work around those limitations (unlikely,
> IMNSHO), there's nothing we can do about this, and nothing we could
> gain by "rethinking".  If you care about these platforms, start
> lobbying the respective development teams to cater more for Emacs and
> its needs.
>
> Sorry.

The silver lining is that I very much doubt PGTK will pose special
difficulties for MPS support.



  reply	other threads:[~2024-06-27  6:09 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ed8ivrw9.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.