rofi VS pass-import

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 always tell these people to just sign up for a password manager and they always resist and say no. I must be missing something obvious.

Maybe they don't want to be relying on a random third-party for all their passwords?

Rather than getting them to sign up for a password manager, what about getting them to install a password manager? I use https://www.passwordstore.org/ - it encrypts your passwords with GPG, and shares the storage via a Git repository for synchronisation between different machines.

That way you can delegate the password handling to another program, e.g. a password manager like pass(1) (https://www.passwordstore.org/) or some interactive graphical prompt.

I want to move to something compatible with https://www.passwordstore.org/ - an open standard for keeping your passwords in a folder encrypted with OpenPGP.

The problem is that I'm nervous to give an unknown Android app and browser plugin total control of my passwords and access to my github account when I don't have time to review it's code properly. I have a bit more trust ing the command line tools, but I'd like to be sure that more people are looking at the code before I trust my life to it.

> Create a system or pattern based on url or brand and mentally hash it into a password.

Doesn't sound very secure. Also when you realize that you anyway have to trust cryptography, I believe it starts making a lot of sense to have an actual cryptographic key and encrypt it with one good random password you learn by heart.

I use pass https://www.passwordstore.org/, which encrypts my passwords with my GPG key, which comes from my Yubikey, which I unlock with a password. That means that I only need to remember one password, and it feels a lot more secure than your pattern based on url or brand.

i use pass and keep my database on a local git repo. it encrypts your passwords with gpg and is a really simple command line program

If you want portability and simplicity, there's a project called simply pass that uses standard *nix utilities (and git, I believe) to manage passwords from CLI.

0. Pass is just text files encrypted with gpg. I needed just one password on one work computer, where I had my gpg key, but not all my passwords. Decrypted the file and that was it.

1. There are plugins and web clients: https://www.passwordstore.org/#extensions

I've been incredibly happy with https://www.passwordstore.org/ for years. The data store is a file hierarchy, with the files themselves encrypted with GPG. Sync is via git. TOTP support with a plugin.