Felix Palmen 📯

#fvwm3 actually merged my "pull request" to add some .desktop file for the #XSession upstream, a topic that came up in a #FreeBSD #ports PR.

It was very quick, and during review conversations, I even learned that KDE delivers a "broken" .desktop file (by FDO standards) which somehow still works 🙈

Anyways, kudos for handling it that quickly. Any porter/packager is thankful for upstreams *that* responsive! 👍
https://github.com/fvwmorg/fvwm3/commit/b3bd394a87d4caab846e1e36be560330901bef27

Add .desktop entry for XSession · fvwmorg/fvwm3@b3bd394

Add a (minimal) .desktop file of type XSession, so fvwm3 is discoverable for display managers following freedesktop.org standards. Fixes #12

GitHub
Aug 3, 2023 at 7:20pmWeb
Show threadjhxAug 3, 2023
@zirias
Congrats on the successful PR! 😉
Show threadFelix Palmen 📯Aug 3, 2023
@jhx I should probably also update the port *again* to include the file that upstream now accepted (which differs a bit from the file added to the port in the first place). Let's see whether I can still do that today before falling asleep 😅
Show threadjhxAug 3, 2023
@zirias
And if not: Tomorrow is a new day 😉
Take it easy 😀
Show threadThomas AdamAug 4, 2023
@zirias It was a pleasure to work with you, Felix. More PRs for other stuff very welcome!
Show threadThomas AdamAug 4, 2023
@zirias I guess as well, I never expected you to learn so much. On the surface, this change was trivial. Just goes to show though. 😀
Show threadFelix Palmen 📯Aug 4, 2023
@thomasadam I probably *should* have looked at the FDO spec in the first place, instead of just comparing to "what is KDE doing", assuming this would be correct 🙈 still really surprised me it wasn't. I meanwhile updated the #FreeBSD port again to deliver the fixed file (who knows, maybe some display manager would choke on it otherwise) until #fvwm3 1.0.8 is done. So, thanks for *thorough* checking! 👍
Show threadThomas AdamAug 4, 2023

@zirias Ha! You’re welcome. This is one of those examples where the spec is in no way followed, yet the users of it don’t care. KDE are a force who won’t give away fuck.

Looking at what other WMs do, they use Application so it for now. One to keep an eye on if the spec changes.

Show threadBartek JasickiAug 4, 2023
@thomasadam @zirias Type=XSession entry isn't broken, but it looks like a non-standardized addition by some Desktop Environments. 😉 It is used to run other Window Manager inside of Desktop Environment instead of the default. For example, to run i3 instead of KWin in KDE. That's why some Windows Managers deliver two .desktop files, one with Type=Application, for Desktop Managers, and one with Type=XSession for Desktop Environments. Generally, a lot of fun. 🤯
Show threadFelix Palmen 📯Aug 4, 2023

@thindil @thomasadam How exactly would that work? I mean, I *did* use #fvwm2 "inside" #KDE a long time ago, but scripted the ~/.xsession for that manually ...

So, if there's some .desktop file for #fvwm3 with "Type=XSession", would e.g. sddm offer me a session "Plasma+FVWM3" or something like that when plasma is installed as well? 🤔

Show threadBartek JasickiAug 4, 2023
@zirias @thomasadam Never used that, I found the information here: https://wiki.archlinux.org/title/KDE#Use_a_different_window_manager. And I also agree, there is no reason to do it, until someone doesn't ask for it.
KDE - ArchWiki

Show threadThomas AdamAug 4, 2023
@thindil @zirias I understand that. But also I don’t really care in the sense that until a category such as Xsession implies behaviour per the standard, every WM is unsupportive of this category.
Show threadFelix Palmen 📯Aug 4, 2023

@thomasadam @thindil I agree it doesn't make sense to rely on some unofficial extension that maybe every "desktop environment" implements differently.

The .desktop file added now will hopefully allow to just pick #fvwm3 for your X session in any compliant display manager. If you want to integrate it with e.g. #KDE (I assume this would still work perfectly fine!), well, write your own ~/.xsession for now 😉