On Tue, Jan 09, 2024 at 10:55:38AM +0000, Simon McVittie wrote: > On Tue, 09 Jan 2024 at 00:27:41 +0100, Andrea Bolognani wrote: > > Just out of curiosity, is there any advantage to having the trailing > > semicolon in this case? We only have a single item in the list after > > all. > > Yes but only a very small advantage. DesktopNames is a value of type > "strings" (string list) and in the .desktop specification, those are > canonically a list of semicolon-terminated items (unlike e.g. PATH, > which is colon-separated rather than colon-terminated, therefore does > not normally have a trailing colon). My reading of the spec is that > implementations are required to tolerate a missing trailing semicolon, > and a trailing semicolon is only mandatory if the last item is an empty > string, which is not true here; but it seemed best to use a > canonical/consistent representation when giving you a recommendation.
Okay, trailing semicolon it is. > > Gtk is probably the most reasonable choice: not only it matches the > > existing default, but it's also somewhat more lightweight in that it > > doesn't drag in a dozen libraries like the KDE implementation does. > > > > Honestly, neither quite fits with spectrwm's aesthetic... We'd > > probably want an old school, unthemed Gtk 2 implementation or > > something like that. Shame it doesn't seem to exist. Oh well :) > > Please don't introduce new GTK 2 software into Debian, even if it's > aesthetically appealing: GTK 2 is dead and will not receive any new > upstream releases, even for critical/security bugs. To be clear, I had no intention of doing that in the first place! I was just wondering out loud which hypothetical implementation would feel the least out of place within spectrwm :) > Apply a flat, > hard-edged, right-angle-cornered theme to a maintained toolkit like > GTK 3 or 4, or a similarly new branch of Qt, if you are looking for a > retrocomputing aesthetic :-) Not a bad suggestion, I might try this just for kicks :) > It's up to you whether to upstream this part. I would personally say > that any reason we give for wanting this change in Debian is probably > equally valid as a reason for wanting this change upstream. The line > I've been drawing for whether to open bugs like this one is that if a > window manager installs into /usr/share/xsessions/, then it's declaring > itself to be a (very small) desktop environment, therefore it should do > "desktop environment" things like expressing a preference for an > xdg-desktop-portal backend. I'll think about it. Upstream might be reticent to accept such a change, so I'll definitely start with the DesktopNames part, which shouldn't be controversial, and then possibly follow up with the portal part. > > I have configured spectrwm to prefer Gtk and > > WindowMaker to prefer KDE, and after using one of the two, logging > > out and switching to the other one doesn't seems to be enough to get > > the other implementation to run: I have to reboot the machine, or at > > the very least kill all user processes even remotely related to the > > desktop portal. > > That's undesired, but also hard to fix. > [...] > > The result is that xdg-desktop-portal continues to run, and its execution > environment still contains the XDG_CURRENT_DESKTOP from the first desktop > environment that you logged into, so as far as it is concerned, nothing has > changed and you still want the first desktop environment's portal backend. Understood. I imagined something along these lines when I noticed that processes would stick around even after closing the session. > Most Debian users choose one desktop environment (per uid) and stick to it, > so this isn't generally a significant problem in practice. Agreed. -- Andrea Bolognani <[email protected]> Resistance is futile, you will be garbage collected.
signature.asc
Description: PGP signature
