unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: emacs-devel@gnu.org
Subject: Re: visible-frame-list (and PGTK)
Date: Sun, 15 Oct 2023 08:54:20 +0800	[thread overview]
Message-ID: <874jisaeo3.fsf@yahoo.com> (raw)
In-Reply-To: <87bkd12en1.fsf@> ("Björn Bidar"'s message of "Sat, 14 Oct 2023 22:22:10 +0300")

Björn Bidar <bjorn.bidar@thaodan.de> writes:

> there are various packages around that e.g. i3 mode that filter
> visible-frame list with i3 ipc to only get the frames from the current
> desktop, similar also ace-window uses such functionality by using
> visible-frame-list or x-window-parameters directly (comparing
> _NET_WM_DESKTOP with _NET_CURRENT_DESKTOP).
> The tried to find any reference that Emacs is doing something similar to visible-frame-list
> by couldn't.

This isn't necessary.  Window managers place frames situated within
non-current virtual desktops in the Iconic state by custom, and such
frames are accounted invisible by Emacs.

Unless i3 contravenes this established practice, such explicit
comparison is unnecessary and expensive.

> For Qt/KDE the kde protocol extension version matches to the current
> version of frameworks, KDE sets the lowest minimum for each version.
> The distro's don't really change that.
>
> KDE and wlroots seem to work together on protocols, e.g. by wlroots
> basing on protocol on the other.

My point is, not enjoying the patronage of those protocols' developers,
we are in no position to maintain up-to-date support for the many
versions that are undoubtedly present on our user's computers.

> My point being that Emacs doesn't agree with the Wayland restrictions
> set by GNOME if the PGTK when using GDK Wayland should match the
> features of the other ports.
> If those features are found in protocols defined by KDE and WLR and are
> also implemented in various compositors using either of them, then I
> think it makes sense to think about adapting these protocols.

Please see above.



  parent reply	other threads:[~2023-10-15  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87h6mta1ld.fsf.ref@yahoo.com>
     [not found] ` <87il79h4ex.fsf@>
2023-10-14 11:24   ` visible-frame-list (and PGTK) Po Lu
2023-10-14 19:22     ` Björn Bidar
     [not found]     ` <87bkd12en1.fsf@>
2023-10-15  0:54       ` Po Lu [this message]
2023-10-14 10:41 Björn Bidar

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=874jisaeo3.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=bjorn.bidar@thaodan.de \
    --cc=emacs-devel@gnu.org \
    /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).