rofi VS sway

https://github.com/svenstaro/rofi-calc together with https://github.com/lbonn/rofi (both packaged for openSUSE and perhaps other Linux distros).

Which rofi you run? The original one from https://github.com/davatorium/rofi (which is Xorg base, so it has to start XWayland) or the Wayland-based fork on https://github.com/lbonn/rofi?

Rofi does not support wayland you should use https://github.com/lbonn/rofi

I think this problem can be solved using Rofi-fork-wayland.

There's a rofi fork that's wayland native and works with the thousands of scripts and themes out there: https://github.com/lbonn/rofi

There's a patched fork of rofi that supports wayland that I'm actually using, but linked the upstream in my OP for general reference: https://github.com/lbonn/rofi#wayland-support

There's a rofi fork that works well in Wayland: https://github.com/lbonn/rofi You need to install this instead of standard rofi

Also, this fork of rofi … https://github.com/lbonn/rofi

There are replacements for dmenu: standard is wofi (https://hg.sr.ht/~scoopta/wofi), but it has slightly less functionality (although many people live with it just fine), or there is port of rofi (https://github.com/lbonn/rofi), which is much more capable (you need this fork, the original rofi is X-only). Both of these are packaged in most Linux distributions.

I wrote my own web based LaTeX editor I can use if I want access to my LaTeX files from a different computer, something I never would have been able to do if I hadn't learned how the pieces work together (though I actually use neovim over ssh more often).

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).