rofi-pass VS bemenu

It's supposed to be cross platform standalone rofi-pass for my Windows. On Linux I use the original one and it's great

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

on my laptop I use: https://github.com/carnager/rofi-pass and https://github.com/qutebrowser/qutebrowser/blob/master/misc/userscripts/qute-pass for qutebrowser integration

Pass combined with rofi-pass

I've made a script called tessen which is, more or less, a replacement of rofi-pass but for Wayland. It can use bemenu or the wayland fork of rofi. It relies on wtype for autotyping instead of using ydotool because ydotool needs a daemon running with root privileges.

rofi-pass is also very nice you already use rofi

Easy to sync because it's a git repo, supports every type of MFA / key under the sun (well, everything that GPG does, because it's basically a frontend for GPG). Easy to programmatically search / create scripts for (I use rofi-pass). Easy to install on a vps and access from anywhere. Most importantly, does one thing and does it well, Unix philosophy.

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.

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.

I've made a script called tessen which is, more or less, a replacement of rofi-pass but for Wayland. It can use bemenu or the wayland fork of rofi. It relies on wtype for autotyping instead of using ydotool because ydotool needs a daemon running with root privileges.