Readit Newsbecause it sounds like Windows is the problem here, doing this screenshotting at all. And Signal allows you to disable the anti-screenshotting measure
Aerospace has a similar resizing glitch as PaperWM.spoon: resizing one direction ends up looking wonky if you do it fast enough. It’s noticeable at the end of the smooth scrolling demo. That must be a macOS thing…
I may check out PaperWM.spoon at some point but realistically I’ll set up a VM and try out Niri
We've adopted the more neutral subtitle now.
First, the tooth is put into the eye — used as biocompatible material to hold the lens. Second, the surgery is 60 years old and has something like a 94% success rate after 27 years, so it's hardly fair to say "surgery _aims_ to restore sight". It almost certainly will restore sight. The part that is interesting in this story is that it's an uncommon surgery that is happening only for the first time _in Canada_.
It doesn't work very well - frequently, the concatenation process is sitting there running long after the client has disconnected. And the devs seem to break it entirely every second release or so, just failing to recognize the BDMV as a playable movie at all.
Say I'm messing around with the commit that introduced a bug, somewhere deep in the history. With git, it's basically impossible to mess up the repo state. Even if I commit, or commit --amend, my downstream refs still point to the old history. This kind of sucks for making stacked PRs (hello git rebase -i --autosquash --update-refs) but gives me a lot of confidence to mess around in a repo.
With jj, it seems like all I would have to do is forget to "jj new" before some mass find+replace, and now my repo is unfixable. How does jj deal with this scenario?
- first, that commit that’s been merged to main is marked as immutable and, unless you add a flag to say “I know this is immutable and I want to mutate it anyway”, you can’t mutate it
- second, as part of your regular workflow, you haven’t actually checked out that historical commit. You created a new, empty commit when you “checked it out” using “jj new old_commit”
- third, you can use jj undo. Or, you can use “jj obs log” to see how a change has evolved over time (read: undo your mass find+replace by reverting to a previous state)