Esme Povirk @madewokherd@computerfairi.es

I just learned a cool git thing.

You can use git switch [revision] -C [branchname] to move a branch to a specific revision and check it out in a single operation. This works even if you currently have that branch checked out.

Unlike git reset, which can do something similar, this operation is safe. If you have uncommitted changes, it'll fail instead of clobbering them.

So at this point I'd always recommend using git restore and git switch instead of git checkout and git reset

Had the thought that maybe I should have compassion for inanimate objects too and not just living things and uh I guess I'm an animist now.

I should probably turn a fan on. doesn't, in order to test this hypothesis

Finally found the "stop nagging me to offer AI" button in Visual Studio

@b0rk No idea. I don't remember seeing those at all.

@b0rk If you think you may have messed up (and your history is linear) because you keep getting "bad" commits: do git bisect log and retest the most recent "good" commit. And the reverse if you keep getting "good" commits.

I also like to do this as a final check after the bisect completes.

If you did mess up, you can use the output from git bisect log to restart your bisect without having to redo any tests.

Probably also applies when using --first-parent but I'm not familiar with it.

Xalia (project I've been working on for about 2 years) is now out there in stable Proton. https://github.com/ValveSoftware/Proton/releases/tag/proton-9.0-2

This is an external program that adds gamepad controls to desktop apps (Linux, Windows, and Wine with some modifications in Proton). Currently only used for a few launchers, but hoping to expand this and have it usable in regular desktop environments.

https://twitch.tv/madewokherd Still doing foot controls and flashcards. Playing Ultimate NES Remix and trying not to get overwhelmed with ILs.

@jyn I'm pretty sure I've had this happen many times and it confuses me every time.

git restore is pretty intuitive compared to git checkout and git reset - I have no idea how I'd fix it with those, probably just do whatever git status tells me until it's fixed.

@b0rk The git clean command won't clean submodules. If I want to clean a project with submodules, I generally run something like this:

git clean -fxd; git submodule foreach --recursive git clean -fxd

@b0rk If you interrupt the process of cloning a submodule, you can end up with files missing, even if you try to update submodules again! HEAD will point to the correct commit but the staging area and working tree will not. git restore -SW . in the submodule should correct this

@octopus If you believe the world is a simulation then it just makes sense.

@b0rk I do read-write constantly, and judging by the replies I'm one of the few who doesn't hate it. It basically forced me to get comfortable working in detached HEAD state.

It'd be nice if git submodule update could keep branches attached.

https://twitch.tv/madewokherd Ubuntu upgrade borked desktop, new streaming setup on Manjaro. Playing Ultimate NES Remix.

Yay, I just made a working PKGBUILD for https://github.com/Stary2001/InputClient-SDL

I'm not sure if I can submit it to AUR though because the author of that program didn't bother with a license.