In the interests of Linux commands generally being short abbreviations, I suggest “pls”.
Try “Bruh”
Bruh shutdown
Maybe pls for the su command?
gooby pls
I’ll fuckin’ do it again, ayuck!
Elite Pink Guy reference
It’s a reference to a comic where Goofy murdered children lol, but yeah, Pink Guy may have said it too.
Or icanhaz
please touch meplease touch my.butt
But the whole reason I use Linux is because I don’t ask it to do things, I tell it to do things, because it’s a machine, and it’s my machine.
You could alias
sudotojustfor a little more rudeness.I’m also not trying to be rude to my machine, that’s erroneous, I’m not going to treat a computer like it thinks or has emotions, one way or the other.
Life pro tip: good manners make it easier to get what you want
ACTUAL good advice?! Is that even allowed here??
Only once per quarter, and only incomplete rules to the advice. This particular instance of advice is barely skirting the standards and norms.
FWIW, using a shell function is preferred (according to Bash docs) and probably a lot more flexible, and less dangerous. No, actually, anything in Linux can be dangerous.
And while I’m also in the camp of trying to make the Basilisk happy, I doubt it’s going to work.
Any superintelligent AI that will extrapolate the past to judge my actions and my innermost thoughts and attitudes won’t be impressed by obeisance. Tell Roko what you really think, and have some self respect. Those Less Wrong types really miss the mark with all that shit.
https://gitlab.com/edneville/please (a sudo alternative)
I prefer an alias that actually reflects my feelings.
alias didistutter="sudo"alias didistutter="sudo !!"I’d recommend this version so you don’t actually have to repeat yourself.
robm@homebox ~$ please su [sudo] password for robm: robm is not in the sudoers file. This incident will be reported.I also like
fuck, which attempts to run the first suggested syntax in the error output of the previous command.What I don’t get is why deny the execution of a command because the lack of sudo instead of just notice that it needs elevated privilege and ask for password
Besides what Ephera@lemmy.ml said, you would also need to handle the escalation at every place you might have a permission related error. Unless your command alwaysneeds to run as root, so you can check once in the beginning, it would be cumbersome and error prone.
Also, sometimes in multi users environments, you might want to execute as 3rd user, not root or your own, if something fails.
It’s kind of bad for scripts, where it can be either annoying or genuinely problematic, when your script hangs on a password prompt. You typically do want it to just fail right away, because if you have monitoring, then you’ll be able to spot it failing.
These days, it is (largely reliably) possible to detect whether a command is being run interactively or as part of an unattended script, so you do see some commands that trigger a sudo password prompt only for interactive use, for example
systemctldoes this. But this adds quite a bit of complexity to each individual program, so it isn’t really something that’s going to be implemented universally.I also have to say that
systemctlkind of gets on my tits when it does that, because it throws up a GUI dialog for grabbing the password, which is quite jarring.
alias thanks="You are most welcomed"please shutdown; thanksI know this is a meme and not GitHub, but I thought some people might like to learn that if you do
please shutdown && thanksit won’t say you’re welcome if the shutdown failedWait, isn’t it the other way around? I thought ; only executed the next command if the previous one succeeded, and && executed the next command regardless of exit status.
No, OP is correct, && only continues on exit 0. || For anything but zero, ; just chains another command.
Ah yes you’re right, had to look it up to see for myself. It’s weird because i remember specifically changing some of my &&s for ; instead because i wanted it to not continue if exit wasn’t zero, but i must’ve misread it at the time. Time to change it back i guess lol.
It makes more sense if you think of semicolons like other programming languages like Java and C use it.
foo(); bar();But those languages allow
foo(); bar();as well. Then&&works like a normal short circuited expression (with side effects).
Partly right in bash:
set -e; echo 1; echo 2;is the same as
echo 1 && echo 2So if you see the
-ein a script, it’s to keep the function clean.
alias thanks="You are most welcomed"you need to use the
echocommand if you want to echo something:alias thanks="echo 'You are most welcomed'"(the inner single-quotes are not strictly required in this case, but recommended nonetheless)
Huh yeah my bad, wrote this too fast in-between two messages at work
alias sudo fucking
fucking systemctl restart firewalld.service
fucking shutdown
Reminds me of my favorite command line utility.
Unfortunately no longer maintained, but in case you didn’t see the other reply: https://codeberg.org/iff/pay-respects
Is their a still maintained fork?
I use Pay Respects now
Kind stranger; you made my day
We need more women in tech.
you can always become the woman in tech
Don’t threaten me with a good time
$ man woman No manual entry for woman🤷♂️
alias srsly="sudo !!"I prefer
"sota !!"
Does that expand properly? My gut feeling is that the
!!expands right away, not when you runsrskybut when you define it.
I have please run the previous command as sudo
i love that!
