Just want to point out that, while it’s a mess in practice, there is a correct place for these files and the problem is that many applications ignore it. Configuration files should be written to an aptly named folder in ~/.config/ (or more precisely, in $XDG_CONFIG_HOME which is set to ~/.config/ in most systems). ~/.local/share/ (or $XDG_DATA_HOME, respectively) is for user data, which is different from config.

Not exactly what you are looking for, but modern shells like fish or zsh (probably?) are good at suggesting completions from history. fzf is another great tool for that. Both are super useful for remembering and repeating commands.

Good clarification and advice.

There are so many considerations when “repairing” an installation, that I would definitely suggest a reinstall here.

Yes, for data recovery you really just need something to access the drives.

If you have backups, reinstall.

If you don’t, boot a “live CD” USB stick and make a backup, then reinstall.

Then think about how this happened and how to avoid it in the future:

I tried updating Kubuntu to the newest version, and it got screwed up the first time,

In either case, its a quick copy/paste on my part, so /shrug.

I was thinking “okay this somewhat unconventional but whatever” until I read this. Use greasemonkey or something for the love of Christ!

Agreed, but use sway instead of i3 for Wayland support.

Pretty sure codeberg.org uses forgejo under the hood.

Another very solid option for self hosting is just adding a git user to a server with git installed, initiate bare repositories there, then talk to them with git@example.com:repo-name