rofi VS bemenu

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

I really like using something like fuzzy search for menus like these. https://github.com/Cloudef/bemenu is pretty cool in that it works both in a terminal, X11 and on Wayland, so if you want to do something graphical later you can easily migrate. There's also fzf and skim, which work similarly but are only for the terminal.

I know that dmenu won't work on wayland, hence I installed bemenu as a drop-in replacement. Now I want to configure keybindings for my scripts using the default settings, but they don't seem to work. Running my scripts from the terminal work, but not when running them via keybinding.

bemenu (i. e. bemenu-run) is a simple launcher that has command line interface (set with BEMENU_BACKEND environment variable), also fzf can be useful in this regard but it will most likely require writing additional scripts to work as a launcher.

I've already highlighted how using environment variables to change themes is a horrible user experience. The bemenu program suffers from the same flaw. Environment Variables should never be used in any way for values that might change inside a running session.

bemenu

Environment variables are fine when used for things that usually don't change once they're set. For example, XDG_CONFIG_HOME or GOPATH. They are, however, absolutely awful when used to configure values that will probably change inside a session. A good example is BEMENU_OPTS from the bemenu program, which is used to change colors, font etc. Should I relogin into my session just to make a program use dark mode colors?

https://github.com/Cloudef/bemenu#environment-variables

In such cases, environment variables lose their intended purpose and they need to be stuffed into wrapper scripts or overridden on the command line before executing a command, which is extremely annoying.

Bemenu - "Dynamic menu library and client program inspired by dmenu"

Instead of rofi, bemenu[2] is nice too.

[1] https://github.com/dunst-project/dunst/issues/264

[2] https://github.com/Cloudef/bemenu

tessen can use either bemenu, the wayland fork of rofi, or wofi to show password store data. It relies on wtype for autotyping instead of using ydotool because ydotool needs root privileges.