From: Lars Ingebrigtsen <larsi@gnus.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: Po Lu <luangruo@yahoo.com>, 57939@debbugs.gnu.org
Subject: bug#57939: 29.0.50; Fixing raise-frame on Sway
Date: Tue, 20 Sep 2022 12:12:44 +0200 [thread overview]
Message-ID: <87pmfqmk0z.fsf@gnus.org> (raw)
In-Reply-To: <87y1uelglr.fsf@yahoo.com> (Po Lu via's message of "Tue, 20 Sep 2022 14:12:00 +0800")
Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> I'm not worried about whether or not Sway keeps the interface stable,
> the problem is whether or not Sway will still be a thing in 2, 5, 10, or
> 20 years.
That is indeed a worry.
> Not to mention that Sway is still a niche compositor, compared to the
> likes of GNOME Shell or Kwin.
>
> If we take the route of supporting non-standard interfaces provided by
> all "popular" Wayland compositors at any given time, then we will
> quickly fall into the rabbit hole of constantly keeping up with changes
> to that status quo.
There's no set rules for any of this -- but we want Emacs to be as
usable as possible across as large a number of systems as possible.
This means that we have a lot of special purpose code in Emacs to work
around oddities in systems, and to interact with specific systems and
libraries.
Sway seems to be one of the major players in the Wayland world, so I'd
welcome code to make Emacs work better under Sway.
prev parent reply other threads:[~2022-09-20 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 16:21 bug#57939: 29.0.50; Fixing raise-frame on Sway Sean Whitton
2022-09-20 1:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-20 5:32 ` Sean Whitton
2022-09-20 6:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-20 10:12 ` Lars Ingebrigtsen [this message]
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=87pmfqmk0z.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57939@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--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).