I also apologize if I was seen as being rude or demanding or condescending but my request was sincere. I don't find that type of conversation to be productive and all I can do when it's directed at me is ask someone nicely to stop. I'll repost the other part of my post because I think it gets to the substance of the issue.
Re global hotkeys: I still don't understand your complaint. You just described two applications that didn't work and then went on to explain how one of them was made to work on Wayland. Yes, applications need to be ported, no solution on the Wayland side will ever change that. If the complaint is that the chosen method adds latency, or that the config setting has moved, those are vastly different than your original complaint which is that it doesn't work. Is that closer to what you were getting at?
> Re global hotkeys: I still don't understand your complaint. You just described two applications that didn't work and then went on to explain how one of them was made to work on Wayland. Yes, applications need to be ported, no solution on the Wayland side will ever change that. If the complaint is that the chosen method adds latency, or that the config setting has moved, those are vastly different than your original complaint which is that it doesn't work. Is that closer to what you were getting at?
Let's compare the workflows.
In X, in order to make guake open by pressing "F12" on the keyboard (which, by the way, is probably the feature that makes guake useful, since its entire purpose is to be a terminal you can pop up with a hotkey), I have to take the following steps:
1. Install Guake
2. Run Guake
That's it (F12 is the default hotkey for guake). It just works.
And it's the kind of thing that's possible on literally every other desktop OS that's ever existed prior to Wayland coming along.
Here's the steps I have to take when using mutter specifically.
1. Install Guake.
2. Realize F12 doesn't work because, in the Wayland ecosystem today, it is impossible for an application to bind a global hotkey.
3. Find a workaround online. Discover "guake-toggle" exists and that I have to manually bind a hotkey to call it.
4. Open the Gnome hotkey configuration screen.
5. Add a new binding for F12. Enter "/usr/bin/guake-toggle" as the command to execute when the key is pressed.
(actually, that's a lie, my vague recollection is you can't actually bind F12 at all in Gnome and so I used F11 as my test... but that's a whole other thing and probably a Gnome bug)
However:
1. This set of steps only works with mutter. For another wayland compositor the steps may be completely different. Or there may be no steps at all if the compositor doesn't have some mechanism to specify a global hotkey.
2. It happens to work with Guake because the author realized a wayland compositor was gonna need a workaround, and they created guake-toggle. For other applications it's possible no such workaround exists at all.
3. It's in any case a profound UX regression.
Now, yes, you can make the claim that guake was "made to work on Wayland".
But if your claim is that therefore nothing is wrong in this situation, I have to admit to simple astonishment and bafflement because I don't know how anyone could not see a problem here.
Now, to be clear: I'm not suggesting this is the sole issue that's preventing my use of Wayland. There is, after all, this crappy workaround.
Rather, as a reminder, this thread started with my replying to this remark:
> I don't understand where you're getting this idea that Wayland is or was supposed to do all the same things as X in exactly the same way.
I hope you can see that my issue isn't that I expect Wayland to "do all the same things as X in exactly the same way".
Rather, I expect Wayland to enable applications to offer the same kind of basic functionality, with the same level of usability, that users are used to experiencing with applications, not just on X, but on any modern desktop operating system.
This is just one example where that's actually not possible today due to immaturity in the ecosystem.
Re global hotkeys: I still don't understand your complaint. You just described two applications that didn't work and then went on to explain how one of them was made to work on Wayland. Yes, applications need to be ported, no solution on the Wayland side will ever change that. If the complaint is that the chosen method adds latency, or that the config setting has moved, those are vastly different than your original complaint which is that it doesn't work. Is that closer to what you were getting at?