To my knowledge, symlinking a Nix file is perfectly fine (though may have interesting behavior with flakes).

https://beepbox.co/ for example

¢-aur — I’m not sure why I pronounce it that way; it’s just how I’ve always pronounced it.

Voyager:

Maybe store project-related stuff in a subdirectory of the project repo, and make everyone on the team get that so I can finally read the other guy’s code.

rg $face memories/ | jq .name

(?=) 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

And neighboring state National Guard cannot (legally) cross states lines without permission.

“Legally” doesn’t matter anymore for anyone rich and red.

Died running indoors with limited space.

Given Trump mention, presumably the US.

FROM scratch AS internet
# TODO

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

This dryer?

There are four boxes to be used in the defense of liberty: soap, ballot, jury, and ammo. Please use in that order.

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.

How does that even work?

(Source)

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