Re:Systemd Rolling Out "run0" As sudo Alternative
by zamadatix on Tuesday April 30, 2024 @04:20PM
(#40215811)
Aliasing the command as the command + your default arguments is the easiest general solution to this kind of problem. I'm not sure if there is a "systemd way" to permanently set it though.
[ Parent
| on HN ]
Re:Systemd Rolling Out "run0" As sudo Alternative
by tolciho on Tuesday April 30, 2024 @06:54PM
(#40217458)
I accidentally compile color support out of st, or set xterm*colorMode:false to avoid seeing the backside of a unicorn randomly rubbed all over the terminal, on account of git and other wares being bad at their inability to not spew color codes. A sensible default would be to set no colors, in the event that the colors are unreadable (due to colorblindness, etc) or distracting, but that ship sailed. Most of my vim config on RedHat linux was disabling wacky vendorisms, and back when I used linux I did have a "special terminal" for some NVIDIA installer that mandated colors to be usable. Maybe the terminal title was set to Fisher-Price, maybe not.
Re:Systemd Rolling Out "run0" As sudo Alternative
by shrimp_emoji on Wednesday May 01, 2024 @09:16AM
(#40222748)
Dang. I wish I had the autism to bristle at colors. Think about all the lost hours agonizing over themes! Not feeling the agonizing tension between the fact that cool-retro-term made your terminal into an awesome monochrome CRT but that it's monochrome green so your syntax highlighting is all messed up!
> back when I used linux
What do you use now? :0 BSD? Plan 9???