xkeysnail VS flatpak

FYI: You can enable them in Gnome with Gnome-Tweaks. Apparently a very recent version of Gnome dropped this functionality for reasons that are beyond my understanding (but that's often the case when I look at the decisions that the Gnome devs make).

However, getting the Control -> Command/Super thing to work is much trickier. The best way is to use this: https://github.com/mooz/xkeysnail

However when I tried that, I ran into all kinds of weird behaviours all over the OS. Also, it doesn't work with Wayland.

If the likes of https://github.com/mooz/xkeysnail/issues/43 are still a going concern then it's not quite as "everywhere" as one would like, and I presume that issue is a fundamental one (i.e. it doesn't sound like XKeySnail gets first refusal on key events).

And I use XKeySnail to have the basic Emacs keys everywhere. I'm sure there are others, but it does enough to keep me happy.

https://github.com/mooz/xkeysnail or the fork of it, I forget it's name, will allow you to do the same as exwm's simulation keys with any window manager.

Thanks for the suggestion guys. I decided to go with xkeysnail ( https://github.com/mooz/xkeysnail/ ). So far so good.

Similar options for Linux users are keyd and xkeysnail

https://github.com/mooz/xkeysnail or something similar ?

Bind everything you want: https://github.com/mooz/xkeysnail

xkeysnail is not bad in the two sense, however, there are some application do can distinguish them, say, chrome and neovide

If you're using x11, there's xkeysnail

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

No, it looks like you have to do it on an application basis.

https://github.com/flatpak/flatpak/issues/2913

Flatpak

> CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections.

nit: This is incorrect. Robust auto-complete scripts call the actual program to provide completions.

That is what Flatpak does. It is Flatpak itself that makes the network connections.

https://github.com/flatpak/flatpak/blob/main/completion/flat...

Not that it would make any differencen if it was implemented in Bash seeing as the Bash script is also provided by Flatpak.

The only performance impact I know of is with the seccomp filter in CPU-bound tasks: https://github.com/flatpak/flatpak/issues/4187

Skimming through the recent comments, there might be a way to optimize some of it.