Sibling from another mother! Tried it a few times over the years here and there just like you, until going full time.

Also got a full homelab going and have been learning python.

I found the article I read about this, which was published a year ago on OSnews. Here’s the link

I read a deep dive into the macos “certified UNIX” thing and it’s a scam. I dont remember the details but the certification is obtained only through a set of testing exceptions. The macos used by people is not the macos that is Unix certified.

As a former macos user (2013-2024ish), macos has become IMO a very user hostile experience. It’s not quite as bad as windows, but macos is not the “user friendly, it (mostly) just works and gets out of your way” os it used to be.

I’m full time Linux now and when I have to use macos or windows I cannot believe how user hostile they both are.

Linux is far from perfect, but at least I control my system/os.

I’m on arch now (BTW) and I’m eyeballing fedora atomic sway.

I gave nixos a shot and pretty immediately noped out. All I wanted as a starting point was nvim with lazyvim. And as you said, it was a huge research project and after an hour with no luck, I nuked it.

I didn’t realize that. Thanks for pointing that out!

It would not, as @Quibblekrust@thelemmy.club explained in their comment (which I neglected to include in my explanation), Bash uses a special variable called IFS when executing for loops like this. IFS stands for Input Field Separators, and is a list of one of each type of whitespace (tab, space, and newline), and uses these as separators automatically.

So instead of taking that whole ls output as one string of text, the for loop automatically separates it into an iterable list of strings using the newline separator.

I was also a teach for a number of years! Hello fellow teacher. :)

I agree. Bash, and GNU/Linux in general is amazing. My recent foray has been into Python, and I’m having an utter blast writing code and learning.

You’ve got a few things going on to be broken down here.

And forgive me if anything I say here seems condescending, it’s not meant to be, I just like to be very explanatory with things like this and to assume the reader may not know anything about anything. (Not as an insult, but simply as a gap in knowledge).

Also, while I’m proficient at Bash, I’m no expert.

LIST=$(ls): Here you’ve stored the output of the ls command to the variable LIST, which gives you a list of items in the given directory, in this case, whichever directory the command is run from. It’s also a good idea to quote the variable assignment like this: "$(ls)".

for i in $LIST;: This is the first part of the for loop statement, which is an iterator, meaning, it will loop or iterate over every item in the given variable/parameter/group of iterable items.

The i here, as you said could be anything. You could say for file in $LIST; or for item in $LIST;. It doesn’t matter, because it’s just a variable name that you are using in the first part of the for statement.

So what bash will do with this is loop over the list, and take each item in the list, and assign it to the variable i, which will allow you do act upon that single item by calling the variable i in some other commands.

do echo "I found one!";: This is the next part of the for loop, which is the instruction set to be executed inside the for loop. Here is where you can act upon the items in your list that have been assigned to the variable i.

In your case, you’re just printing a statement to stdout (standard out), that says, “I found one!”

It’s like saying, for each item in this list, print “I found one!”

So if there are 20 items in the list, it will print that statement 20 times.

However, maybe you want to print the item itself as part of a statement. So instead of “I found one!”, you could do something like:

do echo "I found $i!"

Which then would print “I found some-filename-or-directory-here!” for each item in your list.

done: Finally, the done statement tells bash that this is the end of the for loop. So any commands after the done statement will only run once the for loop has iterated over all items in the list and executed the commands inside the for loop for each item on the list.

A couple of notes:

The ; is used as a command separator or terminator. So bash knows to first run LIST=$(ls) before it attempts to run whatever the next command might be.

In bash, it’s good practice to always quote your variables like so: for i in "$LIST";. This is to avoid errors for characters that might need escaping like whitespace, backslashes, and other special characters.

With that in mind, if you’re running a command like echo "I found $i!", you don’t need to quote the variable again, because it’s already inside a quote set.

Further, it’s not absolutely necessary, but it can also be a good idea to also enclose all of your variables in {}, so whenever you use a variable, you’d do something like: "${LIST}"

This not only more clearly identifies variables in your bash scripts/commands, but is necessary when using bash’s parameter expansion, which is pretty great.

What’s the actual story behind this meme template?

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.

Interestingly enough, this concept was used in pattern making for casting machine parts back before modern machining and parts manufacturing.

They were colloquially called shrink rulers, and looked like a standard ruler, but were actually longer to account for the shrinkage of the material being cast.

For example, say you’re casting a part from iron, which shrinks 1% as it cools, which amounts to 1/8 inch per foot.

An iron shrink rule would look standard, but actually measure a foot as 1 foot 1/8 inches to account for the shrinkage (this is an example and not meant to be actually accurate).

Source: am historian that interviewed pattern makers that used shrink rulers in their work.

Edit: spelling

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?

Absolutely. There are different options.

If you want something simple, just contacts and calendar, check out Radicale. I’ve been running radicals for years and its great.

If you want something more like a whole google suite replacement (contacts, calendar, drive, docs, photos, etc), look at Nextcloud

As a self-hoster, I love docker. It’s been an amazing deployment tool.

WHY THE FUCK DIDN’T YOU ADD .ENV TO .GITIGNORE YOU FUCKING DONKEY!?!?!

I was wondering the same