unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: spacibba@aol.com, avityazev@disroot.org, emacs-devel@gnu.org,
	eller.helmut@gmail.com
Subject: Re: MPS and pgtk
Date: Thu, 27 Jun 2024 09:08:33 +0300	[thread overview]
Message-ID: <86cyo27w9q.fsf@gnu.org> (raw)
In-Reply-To: <m2pls3qbq0.fsf@pro2.fritz.box> (message from Gerd Möllmann on Thu, 27 Jun 2024 05:57:27 +0200)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: Aleksandr Vityazev <avityazev@disroot.org>,  emacs-devel@gnu.org,  Eli
>  Zaretskii <eliz@gnu.org>,  eller.helmut@gmail.com
> Date: Thu, 27 Jun 2024 05:57:27 +0200
> 
> Ergus <spacibba@aol.com> writes:
> 
> >>Looks like pgtk is currently not supported, i.e. apparenlty no one
> >>working on igc is using it, sorry.
> >>
> > This is wondering me because all the main distributions/desktops are
> > moving (or have already moved) to Wayland.
> >
> > 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?
> >
> > WDYT?
> 
> The only thing I prioritize for myself is macOS and that in my fork with
> CL packages :-). Also, the idea that an experimental branch that is
> developed mainly by 2 people should prioritize such things is funny. And
> finally, the assumption that igc has a problem with pgtk or the other
> way around is false.

Let me rephrase this in a more positive way: people who are interested
in having the PGTK build work with MPS are encouraged to come on
board, track this branch's development and the related discussions,
and contribute ideas and patches for that configuration of Emacs.
That's the only way of making sure the branch works with the PGTK
build; it is not a question of changing priorities, because no one of
those currently involved is intentionally neglecting PGTK in this
respect.



  reply	other threads:[~2024-06-27  6:08 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 [this message]
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
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=86cyo27w9q.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=avityazev@disroot.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).