tessen VS bemenu

Looks like a known issue.

https://github.com/keepassxreboot/keepassxc/issues/2281

I'm considering adding support for keepassxc in tessen but autotype works only on wlroots based compositors like sway right now.

https://github.com/ayushnix/tessen/issues/19

This may not be as impressive but I wrote a script to eliminate one of the primary roadblocks I faced when I moved to Wayland on my Linux desktop — a script to copy and autotype password store amd gopass data, kinda like rofi-pass

https://github.com/ayushnix/tessen

tessen is a bash script to autotype and copy password store data on wayland compositors. The latest release of tessen adds support for gopass as well, although parsing YAML files isn't supported. If gopass files use the same format mentioned here, tessen should work fine.

I'd be willing to package it for Void Linux but I don't really have any experience with how Void Linux packages work. tessen is just a shell script so you can download it and place it in your $PATH and use it if you want.

As I've mentioned in the isse tracker here, the only thing that's missing from fuzzel is support for using a configuration file. If it gets that, it would replace every other launcher and dmenu program on Wayland for me and would also allow me to go ahead and brand fuzzel as the default dmenu backend for tessen.

I made this post a few weeks ago about tessen's initial release. Since then, I've added a few features that might've prevented rofi-pass users from switching to Wayland based compositors (I was one of them).

I ran into this problem as well when making tessen. fzf doesn't have a GUI like rofi, bemenu, and wofi do, so you can't use fzf to type in data in anything else besides the terminal in which it was opened, at least not without resorting to ugly hacks (which is what the swaymsg window move method is).

Support for wofi has been added as well

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.