bitwarden-dmenu VS tessen

I believe that I'm not only one who struggling with lack of wayland-native solution of bitwarden with keyboard based‍ UX. Which should be handy to utilize with some wayland tiling window managers like sway, e.t.c. There is a really good script bitwarden-rofi, but it supports only rofi, because of hotkeys-based UI. The second problem of bitwarden-rofi is that it don't work with custom fields. By this fork you can select any field in second prompt after selecting an element in first prompt. It also provides shortcuts by cli flags to select directly password, username or totp. By default, it will use wofi as dmenu client, but it is possible to override selector by any dmenu compatible selector via cli flags. https://preview.redd.it/7efj550jgdb71.png?width=1980&format=png&auto=webp&s=4689c43df7bc6884b484d7f88df3476a496d2f67

By this fork you can select any field in second prompt after selecting an element in first prompt.

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