PoolloverNathan @ PoolloverNathan @programming.dev

Posts

3

Comments

483

Joined

2 yr. ago

bsdtar xf (from nixpkgs#libarchive) and it'll figure it out.

https://beepbox.co/ for example

Yeah, I'm used to NixOS — however, having to edit the config (instead of e.g. a package manager) is a common pain point I see when others use NixOS, and it often leads to them switching distros.

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

A pain point I've seen with NixOS for new users is the focus on editing files — how easy is it for her to install applications that way?

Debian is a stable distro and therefore tends to have less up-to-date packages.

Ubuntu added telemetry and forced snaps

What network topology do you have? My method only assumes server→laptop connectivity (laptop→server and laptop→repo are implied). If server→laptop is unavailable, but you can install Git in general on the server, you could forward the repo through SSH. If Git cannot be installed server-side at all, this is more difficult, and rsync would be the best method I know of.

Detach the laptop's head, then git clone from it over SSH on your build server. When you're done, git push will update your laptop's branches, then you can git push origin the relevant branches on your laptop.

Use F-Droid — the Ripple app that Jagged is referring to has a blue droplet icon.

peddlin', probably. Autocorrect is that 'friend' that acts all sweet until your back is turned.

Do you have any addons that enable contenteditable/designMode?

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.

(to make the joke more obvious)

The two most common sources of security vulnerabilities are buffer overflows, use-after-free, and off-by-one errors.

The point is that many programs completely ignore .cache's existence — when programs do actually use it, adding a backup exception is trivial, but having to manually find what's actually cache in .config (or, even worse, finding one SQLite database with the config and cache) complicates it.

Use a different client — Voyager has a cap on image height.

Have Alt+F bound to wrap the current command-line in a function definition