Yes, that’s what the comment said — smaller PRs are better.

The "+/"* buffers, I assume.

&fras is certainly Uiua, File Read as String

(Kotlin does support that, with the same fun do_thing(arg: Int = 2) syntax.)

Interesting — how easy are they to install compared to Mint, and would there be a way for Mint friends (I have a NixOS config for my fleet, and run our shared services) to easily migrate?

Perhaps it would be useful to list some alternatives?

{ "ok": "false" }

Sending a dump of entire system memory seems incredibly unsafe, to say the least.

Don’t run sha256sum -c on your suspect file — it expects to be passed a file containing hashes and other filenames. sha256sum the iso itself instead and check by eye, or make such a hash file.

https://beepbox.co/ for example

Voyager:

(?=) for positive lookahead and (?!) for negative lookahead. Stick a < in the middle for lookbehind.

It’s equivalent to cp -r, but:

• the copy is read-only
• reuses unchanged files
• easier to share (btrfs sub send)

btrfs sub snap -r

Example code >= Documentation

Yes, with --privileged. It’s totally safe. Trust me.

symlinks (or whatever windows calls them)

Windows actually has two types of symlinks:

• Shortcuts: stored as regular files on disk; only function as a symlink from Explorer.
• Actual symlinks: stored as actual symlinks (or NTFS reparse points). Transparent for all apps, but can only be created using mklink.
• There’s also junction links apparently, but afaik they’re just bindmounts.

moving a symlink can sometimes move all the data too.

Probably, someone managed to create a real symlink in their OneDrive folder, and since OneDrive probably doesn’t check for symlinks it blindly copied all the files to the cloud.

Take all this with a grain of salt — I’m not a Microsoft developer, and it’s been a while since I last used Windows.

Not if you’re a Bash programmer ·υ·

(Source)

It probably opened it in ${VISUAL:-${EDITOR:-vim}}; usually setting one of those variables in e.g. bashrc will avoid future vim.