Kwrite/Kate asks you for password. Seriously, why can’t they all just use pkexec or some abstraction of it?
Sadly, i currently borked all Qt apps on my Gtk setup.
So does Micro. Nano… Nano does not.
Eh, on console i can just do
ssu nano <file>
. Graphical editors are in question.
Lazy vim way I do it:
ggVG"wY:q!
followed bysudo !!
thenVG"wp:x
Grab entire file and stuff it in register W
Exit file
Reopen sudo
Select all and replace with register W them write
Lazier way:
:w !sudo tee %
Yeah learning about
tee
from this thread honestly.It’s been interesting realizing I had such a useful tool at my disposal but never knew
Now I understand how the Adeptus Mechanicus feel when they perform a ritual power-on.
It’s funny how years of use make that so intuitive but spelled out it’s a garbled mess
Is there an editor that can request root privileges without restarting it? That would be quite useful.
i use micro
In vim, in normal mode you can do:
:w !sudo tee %
Apparently that doesn’t work in NeoVim, so recently I installed the suda plugin.
Personally, I just doas nvim and then the file name that needs root access, but it’s a handy plugin in case I forget.
(n)vim + suda.vim.
It’s a simple trick in Vim:
https://stackoverflow.com/a/7078429
For the lazy:
:w !sudo tee > /dev/null %
Sure, you can do this in emacs: https://fuco1.github.io/2017-04-20-Save-write-protected-files-with-sudo-automatically.html
Yeah, in emacs you use
tramp
to open the file with/sudo:
kate
does this in KDE, but it’s not cli.micro ftw, no need to even memorize a command, it’ll just ask if you want to use sudo
C-x C-f /sudo::/path/to/file
I love Emacs. Thanks for teaching me someyhing today
One of the many reasons why I use micro
:w !sudo tee %
Warning: does not work for neovim
I didn’t do any editing since it’s just to prove a point, but I think it does fine.
Neovim, the one true vim, why hast thou forsaken me.
Iirc the specific reason behind this is
- sudo by default requires a tty to run
- vim’s bang spawns a tty to execute commands
- nvim’s bang executes the command directly, then pipes the output to nvim
As a result, sudo (without args) can’t work in nvim as it doesn’t have a tty to prompt the user for passwords. Nvim also used to do what vim did, but they found out spawning the tty was causing other issues (still present in vim) so they changed it.
I am here for one reason and one reason alone: source anime is Watamote, episode 12 @18:36
Tomoko tries to approach a girl, but the wind confuses her and she runs away in embarrassment, even though the girl was really friendly and would have liked to talk to her.
In the meme, this scene is used to parallel the feeling of an external system blocking an operation that both participants would agree to.
A similar feeling could be memed with the “myth of consensual sex” format.
fuck() { sudo $(fc -ln -1) }
This function takes the last command and puts sudo in front of it. Actually used it in a zoom call at work without thinking and it took a second to realize why everyone was laughing. Not my invention–came across it years ago on stackoverflow or someplace and thought it was funny/useful.
kmirl@tux:~$ ls /root ls: cannot open directory '/root': Permission denied kmirl@tux:~$ fuck [sudo] password for kmirl: bin debs docs Mail
Isn’t this the same effect as just running ‘sudo !!’ ?
no because it takes the previous command and adds sudo to it right?
!!
is a shortcut for whatever the last command wasis it not?
According to this super user question, someone said that
!!
won’t work in a function, so you must use thefc -ln -1
command in a subshell instead. Note the response that sayseval
shouldn’t be used (not sure why)Eval shouldn’t be used on userinput. Meaning that if smb other than you may use this to change the system he could put malicious code in the eval part.
Probably doesn’t matter on shell level
Yeah but instead of a function you just make it an alias.
Oh good point, I didn’t think about that
alias fuck='sudo $(fc -ln -1)'
Considering the function name, here’s an obligatory thefuck plug
Use suda.vim for automatically dealing with such cases. Works with
neovim
as well.I’ll also recommend adding the following to your
init.lua
or some config file becausesuda
doesn’t play nicely withnvim -d
orvimdiff
.-- Disable Suda in diff views if not vim.api.nvim_win_get_option(0, 'diff') then vim.g.suda_smart_edit = 1 end
The
vimscript
version of the same would be:if ! &diff let g:suda_smart_edit = 1 endif
sudoedit
is more secure btw. Many editors are not built to be ran as root, and this copies the file to a temo directory, edits it without root, and then overwrites the original file on save with root.