That’s a different form

I think this is good advice. Don’t over-think it!

Seems like a good idea!

Does it relate to stylix or ThemeNix? Does it do something different? (I haven’t tried any of these so I’m not clear on how they compare.)

Modern frameworks like Playwright do a good job of avoiding those waits. So the tests are less flaky, and are faster.

It’s possible (and I think advisable) to set your flake nixos config to set the system flake registry to point to the same nixpkgs revision that your flake uses. The nixos-starter-configs standard template has two lines that do this:

# Opinionated: make flake registry and nix path match flake inputs
registry = lib.mapAttrs (_: flake: {inherit flake;}) flakeInputs;
nixPath = lib.mapAttrsToList (n: _: "${n}=flake:${n}") flakeInputs;

That actually adds all of your flake inputs to the system flake registry. So for example if in addition to your nixpkgs input you also have an input you named nixpkgs-unstable then can also reference that with stuff like nix shell. For example:

nix shell nixpkgs#hello nixpkgs-unstable#cowsay

That’s a good one, and also the first thing I thought of.

There’s also a remake that’s not bad that features Hugh Laurie using his native accent.

A commit followed by a reset or commit --amend later is one more step than a worktree --add. Plus there have been lots of times when I’ve had some changes staged, and some unstaged debugging or experimental changes that I want to make sure not to commit, and thinking about how to pack all that away neatly so I could get back where I was seemed sufficiently obnoxious that I avoided doing whatever would have required a quick branch switch. Worktree would have let me pick up where I left off without having to think about it.

I’ve been using the newer commands like switch and restore for a while. But I learned a few things here that will indeed make my work easier.

They list the “mailing list support” feature as “WIP” so maybe the plan is to accept patches by email in the future?

Until I read the caption I thought I was looking at giant fingers grabbing the dwarf to stick him in the computer slot

Yes, this is what I think of when I think of a “dead man’s switch”. It relates to the concept of a physical device that deactivates or activates if you let go of a switch, like a light saber for example.

I think an interval of weeks would be more convenient than hours to avoid false positives. But I think Patrick Stewart’s character did daily check-ins in the movie Safe House. The dead man’s switch was actually the central plot point in that movie.

You might get better results with rust-overlay - that’s what I’ve been using to cross-compile for aarch64-linux, and for compiling natively on Mac. Let me plug a guide I wrote, https://nixlang.wiki/en/nix/how-to/development-environment-for-rust#setting-a-fixed-rust-toolchain-version

And then the replies to the reporter are also AI-generated!

I love these stories! There’s also,

• radioactive cows
• the high-tide bug
• OpenOffice does not print on Tuesdays

And now that I’ve gone searching for these I see that they’ve all been helpfully collected on http://beza1e1.tuxen.de/lore/index.html