Machinist’s levels usually have adjustment screws on each end: https://www.ebay.com/itm/406571322248

Here’s one in use: https://www.youtube.com/watch?v=ue5W2fwKb4s

“Everything is a file” means that many of the system’s components are represented as abstractions in the filesystem. It’s simply an API that allows reading from and writing to it by integrating into the hierarchical file structure.

If you take a look inside /sys, you will find a fuckton of files, but they don’t represent data stored on a mass storage medium. Instead, the directory contains a mounted sysfs filesystem that contains file-like representations of various parts and properties of the system. For example, you can read them like a file by running cat /sys/block/sda/queue/rotational to check if the sda block device is a spinning disk (1) or solid-state storage (0). Or you can write to them like a file by running echo 1 > /sys/block/sda/devices/delete to command sda’s driver to detach the device. Similarly, /proc contains a mounted procfs filesystem that presents information about running processes as file-like entries; /dev contains a mounted devfs that points to various devices; and /tmp and /run contain tmpfs mounts for temporary storage in volatile memory (RAM or swap).

Windows uses various other APIs (like the Component Object Model and others) to accomplish the same that are not necessarily tied into the filesystem.

It follows the same convention as most programming languages that expose the argument list. Python’s sys.argv has the program name at index 0 and the first argument at index 1. C’s char **argv does the same: index 0 is the program name, index 1 is the first argument. So it stands to reason that Zsh’s $0 should be the program name and $1 should be the first argument…

…which, by the way, is exactly what Bash does as well.

When someone kicks you in the nuts, I hope you remember that it’s actually your fault for having nuts in the first place and not avoiding people who possess legs capable of kicking.

And that means they don’t get to enjoy it if they started watching it later? This post has no value beyond ruining the suspense.

That isn’t incorrect, but it’s not as important as people make it out to be. Linux isn’t certified as POSIX-conformant either.

People are way too stuck on POSIX regarding Fish specifically, but in shell scripting, POSIX compliance boils down to “can it run a pure sh script”. Bash is compliant. Zsh is partially compliant and needs to set an option to emulate sh. Fish uses a different syntax and is not compliant; if that is a problem, don’t execute sh scripts in Fish.

POSIX compliance for shell scripts was important in the 80s and 90s when the #! directive wasn’t as commonly implemented and every script might be executed by the user’s $SHELL instead. That is no longer the case as virtually every Unix-like system’s program loader supports #!.

It’s every person’s responsibility to make sure their mom’s (or dad’s (or other parental figure’s)) vibrator runs only secure, trusted software!

You’re two tubes with a wet sponge between them.

Exactly which flavours of Markdown are targeted/required by this specification?

My heart bleeds for you, you poor oppressed victim of systemic injustice.

The American mind can’t comprehend the freedom to roam.

This meme became popular in early-to-mid 2020. I’m no historian, but I’m pretty sure there were some things happening in early 2020.

deleted by creator

Forcing mundane objects to think is my second favourite neurodivergent obsessions. Especially when you can make a game run a game that is itself.

My examples won’t work because they’re in code blocks. Code blocks are meant to render their content verbatim, without parsing Markdown tags. This span uses multiple formatting tags. ~~**_This is the same in an inline code span._**~~

~~**_This is the same in a code block._**~~

Like I said, spoiler tags are not a standard feature. Whether they work depends entirely on the renderer used by the client.

You’ll have to put that spoiler in a new paragraph. Unfortunately spoiler tags are not a standard Markdown feature. There are no inline spoilers in the Lemmy UI (which is a stupid ass decision, what the fuck devs), and no spoilers whatsoever on Mastodon.

This works:

:::spoiler Spoiler Title
spoiler content
:::

This does not:

:::spoiler spoiler content :::

I’ve played all three games. Arch on PC, Lutris, some GE-Proton 9 version. If the camera acts up in ME2, try Gamescope with relative mouse.

EA App didn’t come up. If it causes issues, try an alternatively sourced copy.