Fusuma VS sway

I don't think there are native gestures in qtile. I use fusuma, since it works better for me on X11 and wayland, but I've also used libinput-gestures in the past when on X11, and that works too.

I'm new to linux, running last version of ubuntu MATE. Tried to get fusuma to have a better experience with my touchpad (I'm using hp notebook). I followed the whole guide for ubuntu on the Github page, created the config.yml using these two commands:

For info, I've been using Fusuma to configure my touchpad gestures and it is awesome!

https://github.com/iberianpig/fusuma this might do the job? I have been using it on Hyprland and, despite the downside of being in Ruby, it works really well and seems stable.

I use Fusuma to manage gestures and have deactivated the COSMIC gestures extension.

The gestures are interpretations of the touch signals that the trackpad provides, and those signals are available to your computer. The gestures and their functions are features of the operating system, but you can define your own gesture with tools like https://github.com/iberianpig/fusuma. Are you mad that the Magic Trackpad does not come with a full set of gesture support for Mint, Gnome, i3, or any of the gosh hundreds of window managers out there? What would you expect to happen to resolve this complaint?

I like using fusuma.

Thx! I actually looked at this, but it only can emulate shortcuts pressing, as I get it. Instead I tried https://github.com/iberianpig/fusuma which has more features and works perfectly with Hyprland.

I use Fusuma to configure my gestures and it is awesome!

you can install fusuma (https://github.com/iberianpig/fusuma) and add their i3 config (https://github.com/iberianpig/fusuma/wiki/i3) for a start

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).