/home/addison

@anon2963@infosec.pub

On this same train of thought: there’s also git sparse-checkout which uses the skip-worktree bit under the hood, and may have an easier interface. I’m not sure though, I haven’t used it yet.

I haven’t seen git update-index --skip-worktree mentioned yet. You can read about the motivation for this feature in the git scm docs.

I have used it in the past when a professor wanted us to clone repos for assignments that included some opinionated settings for VSCode that I didn’t want to use. Skipping the work tree for that directory allowed me to change or delete the config files without git complaining every time I pushed or pulled or whatever, and the changes I made remained local.

You could set up a couple git aliases to “freeze” and “thaw” your config files on the second drive.

I’m a baby dev trying to collect some brain wrinkles. Can you expand that last point? What’s the downside of client side decorations? What’s a better alternative?

It looks like you haven’t passed a package name to nix-search, so it’s just printing the usage info, and fzf is ingesting the lines of that usage info for you to fuzzy search over.

fzf won’t pass the search query back to whatever program piped in the input. The search query is only used to narrow the results.

I’m not sure how to go about interactively searching nixpkgs with fzf, but you could start by writing a function that accepts a package name or whatever you want to search for and passes it to nix-search. Then fzf can narrow down the results for you.

Maybe. Maybe knot.

^I’m ^^so ^^^sorry

The point is that there is now a credible fear that if Biden does not drop out, Trump wins.

Replacing the candidate at the top of the ticket this late is a hail Mary, but it could bring unenthusiastic voters back into the Democratic tent.