> From: Po Lu <luang...@yahoo.com> > Cc: p.d.oli...@mavit.org.uk, 63...@debbugs.gnu.org > Date: Sat, 17 Aug 2024 16:22:05 +0800 > > Eli Zaretskii <e...@gnu.org> writes: > > > Ping! Ping! Po Lu, could you please respond? > > > >> Cc: p.d.oli...@mavit.org.uk, 63...@debbugs.gnu.org > >> Date: Sun, 04 Aug 2024 10:50:53 +0300 > >> From: Eli Zaretskii <e...@gnu.org> > >> > >> Ping! Po Lu, any comments? > >> > >> > Cc: 63...@debbugs.gnu.org > >> > Date: Sat, 20 Jul 2024 12:00:35 +0300 > >> > From: Eli Zaretskii <e...@gnu.org> > >> > > >> > > Date: Sun, 14 Jul 2024 22:00:26 +0100 (BST) > >> > > From: Peter Oliver <p.d.oli...@mavit.org.uk> > >> > > > >> > > FWIW, here is a patch which causes Emacs to check that at least one of > >> > > the environment variables WAYLAND_DISPLAY, DISPLAY, BROADWAY_DISPLAY > >> > > is set before it will try to use PGTK for its initial window. > >> > > > >> > > This patch is not suitable for merging, because it doesn’t consider > >> > > what happens if you try to use PGTK on Windows or MacOS. However, > >> > > people might find it useful if they’re not using one of those > >> > > platforms. > >> > > > >> > > This patch depends on the patch for bug 72118. > >> > > >> > Po Lu, any comments? > >> > > >> > > >> > > >> > > >> > >> > >> > >> > > This is fundamentally an improper approach because there's no predicting > what variables GTK will use in the future. Moreover, it will prevent > Emacs from starting in some Wayland sessions where WAYLAND_DISPLAY is > sometimes not set, and where the libwayland client/GTK simply tries > `wayland-0' or aborts if it's unavailable.
No further comments within 2 weeks, so I'm now closing this bug.
