From: Phil Sainty <psainty@orcon.net.nz>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: "Dirk-Jan C. Binnema" <djcb.bulk@gmail.com>, emacs-devel@gnu.org
Subject: Re: PGTK-related misconceptions
Date: Wed, 20 Apr 2022 15:29:28 +1200 [thread overview]
Message-ID: <2a3a06b390fceb0badf0e4d8aabc34a6@webmail.orcon.net.nz> (raw)
In-Reply-To: <87mtghw4xz.fsf@athena.silentflame.com>
On 2022-04-20 01:58, Sean Whitton wrote:
>> On 2022-04-19 21:10, Dirk-Jan C. Binnema wrote:
>>> I regularly use both X and Wayland, and having to have two emacsen
>>> (and remember to use the right one) just for that seems sub-optimal.
>>
>> I believe there's something called "X-Wayland" for running X programs
>> under Wayland
>
> It's a compatibility layer, basically, and not a great one. I was
> having various basic focus and clipboard problems when running Lucid
> Emacs under Xwayland.
Ah, ok. In that case I guess one really would prefer to install both
builds, if using both Wayland and X at different times.
I imagine one could mostly circumvent the "remember to use the right
one"
issue by automatically setting PATH based on which system you were using
at that time, so that "emacs" was always going to be the correct emacs.
-Phil
next prev parent reply other threads:[~2022-04-20 3:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM5PR03MB3163BBCF9626AD3B88900011C5EE9@DM5PR03MB3163.namprd03.prod.outlook.com>
2022-04-15 2:29 ` PGTK-related misconceptions Po Lu
2022-04-15 7:11 ` Byung-Hee HWANG
2022-04-15 16:24 ` Eric Abrahamsen
2022-04-18 5:18 ` Sean Whitton
2022-04-18 5:31 ` Po Lu
2022-04-18 5:43 ` Sean Whitton
2022-04-18 5:57 ` Po Lu
2022-04-18 18:27 ` Sean Whitton
2022-04-18 19:49 ` Jim Porter
2022-04-19 1:02 ` Po Lu
2022-04-19 2:46 ` Sean Whitton
2022-04-19 2:18 ` Tim Cross
2022-04-19 5:56 ` Eli Zaretskii
2022-04-19 8:13 ` Tim Cross
2022-04-19 10:32 ` Eli Zaretskii
2022-04-19 9:10 ` Dirk-Jan C. Binnema
2022-04-19 10:42 ` Po Lu
2022-04-19 11:53 ` Phil Sainty
2022-04-19 13:58 ` Sean Whitton
2022-04-20 3:29 ` Phil Sainty [this message]
2022-04-20 4:48 ` Stefan Monnier
2022-04-19 16:51 ` Yuri Khan
2022-04-22 5:44 ` Pankaj Jangid
2022-04-18 21:50 Trey
2022-04-19 0:59 ` Po Lu
2022-04-19 3:28 ` Trey Peacock
2022-04-19 4:27 ` Po Lu
2022-04-19 23:02 ` Trey Peacock
2022-04-20 0:48 ` Po Lu
2022-04-20 2:33 ` Trey Peacock
2022-04-20 4:05 ` Po Lu
2022-07-25 21:18 ` Akira Kyle
2022-07-26 2:08 ` Po Lu
2022-07-26 12:10 ` Lars Ingebrigtsen
2022-07-26 12:35 ` Po Lu
2022-07-29 14:26 ` Stefan Monnier
2022-07-30 0:58 ` Po Lu
2022-07-26 21:36 ` Akira Kyle
2022-07-27 2:48 ` Po Lu
2022-07-27 8:34 ` Trey Peacock
2022-07-27 9:10 ` Po Lu
2022-07-27 13:45 ` Trey Peacock
2022-07-27 13:52 ` Po Lu
2022-07-28 1:39 ` Akira Kyle
2022-07-28 2:50 ` Po Lu
-- strict thread matches above, loose matches on Subject: below --
2022-04-20 7:52 Trey Peacock
2022-04-20 8:25 ` Po Lu
2022-04-20 13:13 ` Brian Cully
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=2a3a06b390fceb0badf0e4d8aabc34a6@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=djcb.bulk@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=spwhitton@spwhitton.name \
/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).