The term "keming" is sometimes used informally to refer to poor kerning (the letters r and n placed too close together being easily mistaken for the letter m).
Doing sudo nano will not load your user configuration, sudoedit will. I had plenty of problems with this, but I assume you don't have any custom configuration.
One reason why sometime I don't do sudoedit is that I make a lot of changes to the config/restart service/see it works/edit etc.. sudoedit only write to the file when exiting, so that flow won't work...
for example when having adding a new host on nginx and some configuration and see if everything work (sudo vim/systemc nginx restart/curl https:// domain loop)
but yeah in general i'll just use sudoedit (which alias to se for me) for my root editing
No offense, but that sounds like more OCD behavior. 😅 I don't need or want protection against myself, and I even loath the whole "that's not how you're supposed to do it"-mentality of linux (where when commands know very well what you want, instead of doing it, just tell you you forgot something). 😅
It's not any OCD behavior, but simply the best practices. You've probably at least minimally familiar with the principal of least privilege? The idea is to minimize scope of a potential problem , was it malicious attack or user error, by restricting access to minimum required to perform a task. It may feel like fighting pedantically (and I've been fighting this more than I'd care to) but it will save your ass one day.
Sure, but sudo is specifically designed with security in mind as a security program, whereas text editors are not (although I am more likely to trust vim than vscode). Running a malicious program as the user and not as root can help mitigate the impact it could do, even though it will still be able to do a lot as a user.
Again, like I replied to the other comment, most of the programs you need root for are designed with security in mind and are inherently more secure and have less vulnerabilities than a non security focused program (that is not to say that it is impossible for a security program to have vulnerabilities -it certainly occurred before and keeps occurring- they just have a lot fewer). But even if you need root permissions for a non security focused program, you still shouldn't let any program have it, the whole point is to minimize the surface of attack.
Alternatively you could use my favorite approach, Visual Studio Code. Just open the file with it, edit it and upon saving you will be promoted if the file needs admin rights to save.
Yes, but if you want to argue along those lines, you could also have an infected version of vim on your system just waiting to do malicious stuff until you give it sudo access.
Ctrl-z
kill -9 %1 # Shell keeps track of job pids for you, job 1 is %1, job 2 is %2, etc
fg # Not technically necessary, but it's fun to see the corpse
Ok ok, I know it's a meme, but gentle reminder that :x is :w and :q combined (save and exit). I got taught that in high school (it was a dec unix with real vt120 terminals) and luckily for me I remembered that even if I didn't touch vi for a few years afterwards.
103 Comments
arandomthought@sh.itjust.works · 55 pts · 2y
If they don't understand this, can we even call it intelligent life?
partial_accumen@lemmy.world · 64 pts · 2y
Maybe they use Emacs.
Bonus: I googled "emacs" to make sure I got the capitalization right for the post and Google is throwing shade:
jmcs@discuss.tchncs.de · 25 pts · 2y
Google does the opposite of "vi". Some people just like to watch the world burn.
pirat@lemmy.world · 4 pts · 2y
I misread "the world bum"
Wikipedia: Kerning
TurnItOff_OnAgain@lemmy.world · 12 pts · 2y
Nano forever!
WhiskyTangoFoxtrot@lemmy.world · 3 pts · 2y
edis the standard text editor.hemko@lemmy.dbzer0.com · 7 pts · 2y
Holy shit lmao
dukk@programming.dev · 6 pts · 2y
It’s the other way around, too.
Not as true though.
hemko@lemmy.dbzer0.com · 3 pts · 2y
This gotta be some inside joke leaking from google
dubyakay@lemmy.ca · 6 pts · 2y
Maybe it's time to stop using GOOG
Willem@kutsuya.dev · 4 pts · 2y
oof
possiblylinux127@lemmy.zip · 4 pts · 2y
duck.com
Aurenkin@sh.itjust.works · 2 pts · 2y
Exactly
Octopus1348@lemy.lol · 2 pts · 2y
I don't know how people get this. I tried but it didn't do this.
Skyhighatrist@lemmy.ca · 6 pts · 2y
Strange, I just tried and got the vi suggestion. And, googling vi gave me an emacs suggestion. So shade all around!
hemko@lemmy.dbzer0.com · 2 pts · 2y
Just capitalize it EMACS and people will think you're more senior than in reality
arandomthought@sh.itjust.works · 1 pts · 2y
Well, then my point still stands.
Jk, don't hurt me please!
transientpunk@sh.itjust.works · 1 pts · 2y
Truth
MTK@lemmy.world · 36 pts · 2y
I just shoot myself whenever I want to leave vim
iAvicenna@lemmy.world · 15 pts · 2y
You don't need to be so drastic just shut down the electricity by the main switch
GoosLife@lemmy.world · 17 pts · 2y
I rent a place where I don't have direct access to the main switch, so what I do is I just stop paying utilities until Vim closes :)
EuroNutellaMan@lemmy.world · 7 pts · 2y
Or just shoot the main switch if you at least have a line of sight on it
vrighter@discuss.tchncs.de · 9 pts · 2y
you can just unplug your pc: and that way you won't incur downtime for the rest of the house.
pineapplelover@lemm.ee · 3 pts · 2y
You haven't shot yourself yet though so you're still in vim
MTK@lemmy.world · 2 pts · 2y
You don't know!
vsis@feddit.cl · 35 pts · 2y
wrong: you press esc multiple times to make sure you are in normal mode.
treadful@lemmy.zip · 15 pts · 2y
At least 3 times. 5 to make sure.
doctorn@r.nf · 25 pts · 2y
sudo nano
hemko@lemmy.dbzer0.com · 23 pts · 2y
You shouldn't really use editor with sudo, but instead use sudoedit to edit files restricted to root user
SUDO_EDITOR=nano sudoedit /etc/fstabThis accomplishes the same function while running the text editor as unprivileged user
doctorn@r.nf · 10 pts · 2y
Why?
Files from user: nano
Files from root: sudo nano
Files from another user: sudo nano (and if new sudo chown after)... 😂
Never had any problems with this in over 10 years... 😅😂
Hawk@lemmy.dbzer0.com · 14 pts · 2y
Doing
sudo nanowill not load your user configuration,sudoeditwill. I had plenty of problems with this, but I assume you don't have any custom configuration.samuelc@lemmy.world · 9 pts · 2y
One reason why sometime I don't do sudoedit is that I make a lot of changes to the config/restart service/see it works/edit etc.. sudoedit only write to the file when exiting, so that flow won't work...
for example when having adding a new host on nginx and some configuration and see if everything work (sudo vim/systemc nginx restart/curl https:// domain loop)
but yeah in general i'll just use sudoedit (which alias to se for me) for my root editing
doctorn@r.nf · 3 pts · 2y
I just have a root custom config too. 🤷♂️ This even allows me to easily use different configs for root than for the user.
Made with 'sudo nano', fyi. 😂
hemko@lemmy.dbzer0.com · 3 pts · 2y
As mentioned, to prevent running your text editor with root permissions. It's just security optimization
doctorn@r.nf · 4 pts · 2y
Let me rephrase my question:
Why would I not want to open nano as root?
No offense, but that sounds like more OCD behavior. 😅 I don't need or want protection against myself, and I even loath the whole "that's not how you're supposed to do it"-mentality of linux (where when commands know very well what you want, instead of doing it, just tell you you forgot something). 😅
Swiggles@lemmy.blahaj.zone · 4 pts · 2y
doctorn@r.nf · 2 pts · 2y
But, in that example:
If I'm the admin it doesn't matter I use it.
If I'm not it's not my problem that I could get more privileges than allowed. I'd probably even use the possibility then. 😅
So it poses a risk if you allow none-admin users to do that on your system, but I still don't see why I must choose to not use nano as root myself. 😅
Anyway, good practice to me is ease-of-use instead of with 7 protections against things that rarely happen.
Like, I'm pretty sure you are better protected from burglars if you also lock all doors inside your house, but I'm definitely not doing that either. 😅
Edit: Also, if you have users on your system, just chroot/vroot/lxc them, so they be free to 'sudo nano' too... 😅
Swiggles@lemmy.blahaj.zone · 3 pts · 2y
hemko@lemmy.dbzer0.com · 1 pts · 2y
It's not any OCD behavior, but simply the best practices. You've probably at least minimally familiar with the principal of least privilege? The idea is to minimize scope of a potential problem , was it malicious attack or user error, by restricting access to minimum required to perform a task. It may feel like fighting pedantically (and I've been fighting this more than I'd care to) but it will save your ass one day.
scinde@discuss.tchncs.de · 1 pts · 2y
It's probably to protect against any potential security vulnerabilities in the text editor program itself, not to protect you from yourself.
doctorn@r.nf · 3 pts · 2y
Wouldn't that logic count for anything, including sudo itself?
scinde@discuss.tchncs.de · 2 pts · 2y
Sure, but sudo is specifically designed with security in mind as a security program, whereas text editors are not (although I am more likely to trust vim than vscode). Running a malicious program as the user and not as root can help mitigate the impact it could do, even though it will still be able to do a lot as a user.
veniasilente@lemm.ee · 2 pts · 2y
You can say that just about anything.
sudo grub sudo boot sudo root=/dev/disk/linux sudo kernel-6.1.image sudo init sudo elogind sudo xterm sudo bash sudo nano
scinde@discuss.tchncs.de · 3 pts · 2y
Again, like I replied to the other comment, most of the programs you need root for are designed with security in mind and are inherently more secure and have less vulnerabilities than a non security focused program (that is not to say that it is impossible for a security program to have vulnerabilities -it certainly occurred before and keeps occurring- they just have a lot fewer). But even if you need root permissions for a non security focused program, you still shouldn't let any program have it, the whole point is to minimize the surface of attack.
Huschke@lemmy.world · 7 pts · 2y
Alternatively you could use my favorite approach, Visual Studio Code. Just open the file with it, edit it and upon saving you will be promoted if the file needs admin rights to save.
LaSaucisseMasquee@jlai.lu · 7 pts · 2y
Okay but how can I show how good I am with shortcuts to edit legacy software ?
Huschke@lemmy.world · 2 pts · 2y
Vscode does have a lot of shortcuts, so you could always study them in detail and impress others that way. 😅
MalReynolds@slrpnk.net · 3 pts · 2y
Yup, s/vsc/kwrite/ personally, it's lighter, but why shouldn't I have a pretty for my config editing needs...
hemko@lemmy.dbzer0.com · 2 pts · 2y
I love vsc but it's not always available.
doctorn@r.nf · 1 pts · 2y
So for any supposedly malicious activity (infected) it wants to do, it just has to hold until you save and give admin access? 😅
Huschke@lemmy.world · 2 pts · 2y
Yes, but if you want to argue along those lines, you could also have an infected version of vim on your system just waiting to do malicious stuff until you give it sudo access.
doctorn@r.nf · 0 pts · 2y
Indeed... Hence why I use 'sudo nano'. 😜
SigHunter@feddit.de · 23 pts · 2y
until the moment you realize that somehow you are not on your native keyboard layout and where the hell is : and ! in this weird language??!
lseif@sopuli.xyz · 10 pts · 2y
ESC Z Z
JetpackJackson@feddit.de · 4 pts · 2y
I have done this too many times now lol, you'd think I would have learned
MacNCheezus@lemmy.today · 22 pts · 2y
"I use Arch Linux btw"
*doesn't know how to use vim
Pottery
ILikeBoobies@lemmy.ca · 2 pts · 2y
Hey!
marietta_man@yall.theatl.social · 20 pts · 2y
ESC Z Z
Although I usually bang ESC a few times to
make sure i’m back to command mode
lseif@sopuli.xyz · 13 pts · 2y
you mean normal mode?
marietta_man@yall.theatl.social · 3 pts · 2y
Yes, I do.
digger@lemmy.ca · 6 pts · 2y
Double Z's will save and then exit. The command on until board will exit without saving changes.
Astaroth@lemm.ee · 3 pts · 2y
yeah to exit without saving you do ZQ instead of ZZ
topinambour_rex@lemmy.world · 3 pts · 2y
Shouldn't be Z Z esc ? Because, you know ZZ top.
rattking@lemmy.ml · 17 pts · 2y
al177@lemmy.sdf.org · 11 pts · 2y
I think you meant :r!:(){ :|:& };:
TimeSquirrel@kbin.social · 17 pts · 2y
Yanks power cord
BatrickPateman@feddit.de · 4 pts · 2y
EuroNutellaMan@lemmy.world · 1 pts · 2y
Slumps up the yummy battery acid
_cnt0@sh.itjust.works · 17 pts · 2y
Great, now all my changes are lost. Thank you very much!
possiblylinux127@lemmy.zip · 12 pts · 2y
Your welcome!
greyhaven7@lemmy.world · 1 pts · 2y
wq
_cnt0@sh.itjust.works · 1 pts · 2y
Thanks Sherlock.
key@lemmy.keychat.org · 11 pts · 2y
Ctrl-z
ps
kill -9 pid
fg
WaterWaiver@aussie.zone · 7 pts · 2y
Alternative:
possiblylinux127@lemmy.zip · 6 pts · 2y
SpaceCadet@feddit.nl · 3 pts · 2y
Reminds me of the time I brought down a whole AIX server with the
killallcommand back in the 1990s.On AIX
killallreally means kill every single process.Im_old@lemmy.world · 10 pts · 2y
Ok ok, I know it's a meme, but gentle reminder that :x is :w and :q combined (save and exit). I got taught that in high school (it was a dec unix with real vt120 terminals) and luckily for me I remembered that even if I didn't touch vi for a few years afterwards.
Dasnap@lemmy.world · 5 pts · 2y
Funnily enough, I knew of :x before :w.
cupcakezealot@lemmy.blahaj.zone · 8 pts · 2y
i think you mean ctrl s and ctrl x
possiblylinux127@lemmy.zip · 3 pts · 2y
That didn't work
selokichtli@lemmy.ml · 1 pts · 2y
Still on it!? Are you, people, immortal? =)
cupcakezealot@lemmy.blahaj.zone · 3 pts · 2y
nano is forever
glowie@h4x0r.host · 7 pts · 2y
What is this sorcery?! I thought you had to reboot each time to exit.
kbotc@lemmy.world · 5 pts · 2y
META-C :wq!
ESC is all the way over there and my hand is already on the space bar.
evranch@lemmy.ca · 2 pts · 2y
Especially as a Dvorak user CTRL-C is effortless. Reaching for ESC makes zero sense!
PoolloverNathan@programming.dev · 1 pts · 2y
ALT-: wq!
Saved you a keypress
XTornado@lemmy.ml · 1 pts · 2y
Not if you swapped the caps lock with ESC.
Tenthrow@lemmy.world · 5 pts · 2y
That's only if you don't want to save first (ahem write the buffer).
Jorgelino@lemmy.ml · 9 pts · 2y
Odds are if you don't know how to exit vim you probably don't want to save whatever you wrote in there.
possiblylinux127@lemmy.zip · 8 pts · 2y
Who in there right mind would want to save a bunch of gibberish
QuazarOmega@lemy.lol · 4 pts · 2y
ihh splqqiq:wq
Wear your mistakes proudlyq!
Turious@leaf.dance · 3 pts · 2y
But I don't want to stop.
possiblylinux127@lemmy.zip · 3 pts · 2y
Oh no....
veniasilente@lemm.ee · 3 pts · 2y
Joke's on them I'm using Emacs as an OS so when I want to exit vi I just
C-a M-exit C-r C-y.Zardoz@lemmy.world · 3 pts · 2y
I prefer ctrl-[ instead of escape
vrighter@discuss.tchncs.de · 2 pts · 2y
That's the first one i've learned to use and I have a hard time actually using the escape key. it's just so out of the way
Shareni@programming.dev · 1 pts · 2y
That's why you rebind caps to:
hold = ctrl
tap = ESC
Kmonad is my favourite tool for this, but there are other options.
Bonus: rebind hold ret to ctrl and you can C-[ with one hand, and it makes navigation a lot easier if you can't palm ctrl
pirrrrrrrr@lemmy.dbzer0.com · 2 pts · 2y
[ESC] wq
Astaroth@lemm.ee · 2 pts · 2y
ZQ
user1234@lemmynsfw.com · 1 pts · 2y
From phone: ssh user@server killall vim
Count042@lemmy.ml · 1 pts · 2y
ZZ