[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: visible-frame-list (and PGTK)
From: |
Po Lu |
Subject: |
Re: visible-frame-list (and PGTK) |
Date: |
Sun, 15 Oct 2023 08:54:20 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
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.