Nix really has a kickass way of doing this. Won’t conflict anywhere and always let’s you know what is managed by Nix.
Nix really has a kickass way of doing this. Won’t conflict anywhere and always let’s you know what is managed by Nix.
Great username
I like this as an idea, but there’d need to be some sort of automatic hooking for me to want to use it. eza/lsd are good enough for ls output for me.
Doing stuff like this is much more cozy in nushell, since piping is a lot less messy
I find myself writing way less stuff like this since making the switch…partially because they output of a lot of builtins is already pretty.
Sounds good in theory.
But I’ve had so many issues with D-Bus fucking shit up on my systems that I’d be very reluctant to hinge my only way of recovering from failures upon something so brittle.
Granted, D-Bus hasn’t given me any trouble since moving to NixOS. The hell of trying to recover my arch systems from a perpetually failing D-Bus would make me very apprehensive to adopt this. I could see myself using run0 by default, but keeping sudo-rs or doas around with a much stricter configuration as a failsafe until the run0 + D-Bus + PolKit is absolutely stable and bulletproof.
What about this situation where kids don’t have enough knowledge to give informed consent to being spied on and profiled for the rest of their adult lives?
Useless manager detected
I’m guessing it writes user data back to the USB
use flakes
ollama run <some_model> "query" | shellcheck | wl-copy
What the terminal needs is better discoverability. Maybe command recommendation if it isn’t going to hallucinate flags and paths that don’t exist. All this bullshit is just some company trying to capitalize on that desire.
The entire board