I'd drop keepassxc and pick up GNU password store or gopass. Pgp+git and a nice cli to wrap them onto an encrypted password store that's pretty easy to move around these days.
The tool, unless something has changed in the meantime, has one major drawback for me. The filename of the encrypted files is displayed in plain text. However, I don't want people to be able to see, for example, which Internet sites I have an account with. Sure you can name the files otherwise. But how should I remember for example that the file dafderewrfsfds.gpg contains the access data for Mastodon?
In addition, I miss with pass some functions. As far as I know, you can't save file attachments. Or define when a password expires. And so on. Pass is therefore too KISS for me.
Pgp+git and a nice cli to wrap them onto an encrypted password store that’s pretty easy to move around these days.
A matter of opinion, I would say. I prefer my Keepass file which I can access via my Nextcloud instance or which is stored on a USB stick on my keychain.
By the way, the file is secured with a Yubikey in addition to a Diceware password. So saving it in the so-called cloud is no problem. Just as a note, in case someone reading my post wants to make smart remarks about the cloud.
For me, this is the main reason why I use micro. And because I don't like the handling of vim. Funnily enough, I've been playing around with Helix for a while now and I really like the editor, even though it's a modal editor, just like vim. Maybe because of the selection → action model. The question is, do I like Helix better than micro? I still have to answer that question for myself at some point.
Basically, a "handcrafted" cmatrix with compilation flags focused on optimization and the musl library (which is "technically better" than glib, a standard library on most distros).
Do feel free to try it out however, its only 139KiB -- click here.
tl;dr guide on how to get it running
1- Install docker (docker on most distros -- docker.io on ubuntu and friends)
2- sudo usermod -aG docker (addyourusernamehere)
3- reboot
4- run it with "docker run -it --rm --log-driver none --net none --read-only defnotgustavom/cmatrix:marchedition"
This is just a matter of personal preference, but I can't stand libreoffice UI. It has more features but I don't open office documents much, mostly just some basic spreadsheets, so I can get away with using a document editor with less feature but easier to the eye.
To add to all great comments here I have one that I’ve used for ages and not seen mentioned here: lftp
It supports many protocols for ftp like over ssh and allows for shaky connections with resume and back in the days when this was more common I used to just run it in the background to download huge files that took days to download and it would gracefully just reconnect/resume/retry until done.
+1 for fish shell. The lack of POSIX compliance really doesn't matter at all day-to-day, but all the qol features that the shell has absolutely do matter and they are so worth it.
Fossil I've never tried, but I utterly hate git. Nothing about how it works makes sense to me. Mercurial is, in my opinion, better-designed and easier to understand for my rather simple use cases. (I should note that I graduated from university around the time svn was replacing csv, so I was coding before there was such a thing as distributed version control.)
qalculate - the most powerful calculator I've seen. There are qt, gtk and cli versions of it.
moreutils - collection of tools. My favourite is vidir, it opens directory structure in your terminal text editor, so that you can rename multiple files easily.
Correct, the reason they are called packages, is that the package can contain other resources besides usable programs, like libraries used by other programs.
It's a signed archive of deployable files along with meta-data. Usually a cpio archive (which is similar to a tarball) with that extra signature wrapper and meta-data (which, itself, should be a list of files and checksums).
A proper package can validate a project's installation, either from the local database or from remote resources, at any time, which gives positive assurance that what is installed is what should be installed.
As well, proper package info is exported by SNMP to be consolidated centrally and validate what is vs what should be installed at the group level.
TL;DR? Like a tarball with tracking info, signatures, checksums, and top-to-bottom validation. If it's a good package, anyway.