I should have added a /s.

Canonical controls the back end and that (along with how canonical has treated snaps in Ubuntu pulling them in with apt calls) are two major reasons snaps get (justified) hate

The huge benefit (to canonical) is that they control the store/repo.

Come on gang! We all know the real answer is Hannah Montana!

+1

To check for an empty string, use -z. -n checks to see if a string is not empty.

jq is indispensable

To be clear, flatpaks from flathub. Fedora has their own flatpak repository, and those are not the flatpaks you are looking for.

Holy shit. I just tried it. ctrl+r is a revelation! How the fuck did I not know about this?

It has a fingerprint reader.

What do you like about chezmoi vs stow?

I don’t share mine. I manage them with gnu stow and my private gitforge on my server (with 3-2-1 backup in place)

I don’t have an objection to sharing them. I don’t think it’s too personal, I just don’t use a public facing gitforge.

Edit to add: I have branches for my different machines in my dotfiles repo for variations

I run arch on my laptop (btw), and Ubuntu server on my server. I like how reliable and stable Ubuntu server is. Gives me piece of mind.

I’ve already aliased gl for git log with my flags, but have been too lazy to add more aliases.

Oh. I did not know that. Gonna try that right now.

jq is indispensable.

zoxide. It’s cd but better. It remembers which directories you’ve navigated to, and fuzzy finds them.

So instead of typing:

cd /really/long/path/to/sime/dir

You can type:

zoxide dir

And it’ll take you right to the directory.

I’ve got it aliased to zd so I type:

zd dir

And I’m there.

Thank you for the link!

I do understand the logic and the difference between ;, &&, and `||. What was confusing me was the command grouping and my misunderstanding of the curly brace grouping rule that the command list has to END with a semicolon. @SheeEttin@lemmy.zip pointed out to me with the link in the comment they left.

I had read that same link and misunderstood it. On second read I got it, and see now why my script is working, as the newlines serve the same purpose as the semicolon, so the curly braced groups are terminated correctly.

My environment is just my homelab. Ubuntu server on my server, Arch (btw) on my laptop. So I could go with any language , but right now I’m choosing Bash. I know stuff I’m doing would probably be easier in a different language, and maybe I’m a glutton for punishment. I just want to get really good with Bash.

The logic is Bash is gonna be available on just about any computing environment I encounter (linux especially, but even Windows with WSL and zsh on macOS (which I know is different, but still very similar). But really, I am just enjoying the hell out of learning and scripting with Bash. I’ll move on to Python or something someday.

Ah! I misinterpreted what I read! I found that exact same reference link when looking into this and I misinterpreted this:

The semicolon (or newline) following list is required

to mean that it required the semicolon as the command separator. That explains why my script works. The newline closes each group, and the other operators are allowed, the list just needs to be closed. Thank you!

+1

I’m having a ton of fun learning and scripting in bash!