Ah, sorry. I was answering about hyper.

The earliest reference to “meh key” I’m turning up on Kagi is from ErgoDox’s Indiegogo in 2015.

They may have coined the term.

That would be the Space-cadet

The digital zoom is doing cool things to its feathers.

Google Camera?

Frutiger Aero, I think.

What does a Pixel 9 Pro do that a $200 retail Moto G doesn’t?

Laser thermometer.

Also GrapheneOS’s requirements.

I went Galaxy S22 Ultra (ultrasonic) to Pixel 8 Pro (optical) to Pixel 9 XL (ultrasonic).

My impression was the performance improved over time with the Galaxy and Pixel 8. I find the Pixel 9 worst overall, but figure they’ll improve it in software.

No data to back that up.

It mostly struggles when my hand is wet. I miss the Pixel 4’s face unlock.

Try to use open source software. Harder for it to disappear.

You can’t build a box that will survive long without your help. You’re maintaining a living system, not a sculpture. It needs someone at the wheel making decisions. Updates will have breaking changes. Tokens and certificates will expire. Eventually hardware will fail.

The best you can do is provide an easy way to export the important data into a digestible format for your loved ones to manage with the skills they have. If that means pushing it into a managed service owned by Big Tech, so be it. You don’t want to tacitly hurt them for their lack of interest in self-hosting.

I use it all the time for hot drinks and soups.

I came into Emacs (only a year ago) with Vim experience as well, and it was a difficult transition for the reasons you describe, but I persisted due to the beauty and power of the rest of Emacs’ design and ecosystem.

I try to use the default bindings whenever possible, as I find going against the grain in Emacs leads to less efficiencies as packages stop cooperating with me or each other. Evil-mode is often criticized for this reason. It clobbers other bindings.

Understand that the default editing functions work best for lisps and their sexps. You will likely need to find third party packages to get that fluid feeling back for non-lisps. (Or implement them yourself!)

Check out

• change-inner which uses expand-region
• Maybe even the heavy-handed evil-mode. (But if you do, I’d recommend considering Meow as a less-invasive alternative)
• wgrep combined with the replace- commands really impressed me.

Sorry to break it to you, but that’s a bot.

At least it’s level on a table because of the bar

I have access to Into the Breach and Slay the Spire on Android but not in my Steam library. I’d enjoy first party support in playing them on my Deck.

Android games on Steam Deck.

The OP didn’t mention Proxmox in their post. I’ve been speaking generally, not about any specific OS. For example, Nvidia’s enterprise offerings include a license to use their “GRID” vGPU tech (and the enabled feature flag in the driver).

Why? Product segmentation I suppose. Last I looked, the Virtio project’s efforts were still work-in-progress. The Arch wiki article corroborates that today. Inconsistent behavior across brands and product lines.

I’ve also wanted to do this for a while, but there were always a few too many barriers to actually spin up the project. Here’s just a brain dump of things I’ve seen recently.

vGPUs continue to be behind a license. But there is now vgpu_unlock.

L1T just showed off PCIe “fabric” from Liqid that can switch physical devices between machines.

Turning VMs on and off isn’t as slick as either of the above, but that is doable today. You’ll just have to build all the switching automation yourself. That could just be a shell script running QEMU/libvirt commands, at a minimum.

Thanks for asking. Not sure how I toggled that on…

You can put the game into its own time namespace.

https://www.man7.org/linux/man-pages/man7/time_namespaces.7.html

I’m not sure I understand your question.

Eat has its own major mode which is used when you open a standalone buffer via the eat function.

When it’s embedded in Eshell it mostly just does the right thing whenever you invoke a command that uses terminal control codes (e.g. htop) – and many of those can be closed with q, yes.

I assume Eat is activated for any program listed in the eshell-visual-commands variable (but I’ll admit I don’t really understand how that works). The notable new minor modes present when I run htop in eshell are Eat--Eshell-Local and Eat--Eshell-Process-Running.