st VS keepassxc

> you need to "edit your makefile". That isn't going to work for distributions

Is it not? [st] requires exactly that. And distros seem to have no issues shipping it.

[st] https://st.suckless.org/

I am fundamentally and ideologically opposed to using a terminal emulator implemented in electron.

If you feel similarly, then you might enjoy https://st.suckless.org/

You can use different forks of the ST. I, for example, use this one, already with the necessary patches https://github.com/mrdotx/st

kiss with kiss-xorg, nsxiv, st, dmenu with script, tewi, fet.sh

My journey of using terminal emulators began together with my introduction to Linux about 7 years ago. GNOME terminal was my first as it came pre-installed on Ubuntu, my first Linux distribution. Since then, I've had the opportunity to explore and utilize a range of terminal emulators, including Alacritty, Kitty, st, Konsole, xterm, and most recently iTerm2. It's been interesting to experiment with these different emulators, each offering its unique features (or similar however with each with personal touch), user interfaces, and performance benchmarks. Just the other day, a new terminal emulator caught my attention: Warp Terminal. My curiosity won, and Warp was downloaded, this short blog are my thoughts about Warp terminal. At the moment there is only support for macOS, however linux and windows builds are on the way.

Terminal : st

For those looking for a minimal VT100 terminal emulator without the legacy baggage of Xterm, I highly recommend checking out Suckless Software’s st: https://st.suckless.org/

That last reference builds off of the work of the other two. It also breaks down how NOT modern Xterm is, but, if I've read it correctly, it confirms that its input latency is low compared to all other tested terminal emulators, including Alacritty and ST, which humorously and justifiably thrashes Xterm on its homepage for being a bloated program. Its not a good choice for everyone: it has poor right-to-left text and Unicode support, making working with Chinese, Arabic, and other alphabets not great, I've read.

ST is a favorite of some fervent minimalists. I do not think you would like it.

KeepassXC supports exporting, but i don't think it is released in a stable version / to the public yet:

https://github.com/keepassxreboot/keepassxc/pull/8825

If you use KeePass, make sure you use the KeePassXC variant. KeePass is dead.

https://keepassxc.org/

That's why you use the superior one, KeePassXC, as linked in the NIST link: https://github.com/keepassxreboot/keepassxc/discussions/9433

Over there, they got pissed about people constantly bugging them about it and closed the bug with the last comment reading:

for the internet, use a password manager like keepassxc with a strong password.

Another regression is that KeePassX/C AutoType doesn't work with Wayland, so now instead of a simple CTRL+V in KeePassXC, I have to separately copy and paste the user and the pass.

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

That's really a shame, I know keepassxc has (recently) added support for passkeys, but does it also support import/exporting them? I only found this comment[0] in the github issue.

---

0: https://github.com/keepassxreboot/keepassxc/issues/1870#issu...