ZZ
:qa!
ZZ
Serious question. Why? No, for real, why? Why are these hard to understand editors still the default on most distros and flavors? Why haven't they reinvented themselves with easier to understand shortcuts?
I get the feeling my comment will attract heat, but I'm a web dev, studied comp Sci for years, have worked for nearly a decade and have spent over half my 30 year old life using computers of all sorts. I'm by no means a genius and I by no means know enough about this or most tech subjects, but I literally only knew how to close vim with and without saving changes in a recent vim encounter, purely due to a meme I saw in this community a few days prior, and I had already forgotten the commands by the time I saw this post. Nothing about vim and alternatives feels intuitive or easy to use, and you may say it's a matter of sitting down and learning, which you can argue that, but you can't argue this isn't a bit of a gatekeeper for people trying to dip their toes into anything that could eventually rely on opening vim to do something.
I won't try to deny its place in computer history, or its use for many, or even that it is preferred by some, but when every other software with keyboard shortcuts agrees on certain easy to remember standards, I don't quite understand how software that goes against all of that hasn't been replaced or hasn't reinvented itself in newer versions.
Then again, I have no idea what the difference between vi, vim, emacs, and nano are, so roast away!
Because vim (and emacs too!) is a powerful editor that works purely on command line and most people who are experienced in the Unix world are generally familiar with it. There are plenty of easier editors to use, like nano, that are also widely distributed and you are free to change your default. Being really powerful but you kind of need to know what you're doing is basically unix's whole thing.
Nano is the default on Debian for more than a decade. Maybe two. I don't think vim is the default on any largely use distro now.
Are you actually asking why people use them?
I guess some people really like the features. Imo Micro/Nano are much easier to use than Vim
Why are these hard to understand editors still the default on most distros and flavors
I think nano is usually the default nowdays. Nano os pretty minimal and has it's keybinds always on display so you don't need to memorize them.
Why haven't they reinvented themselves with easier to understand shortcuts?
Nothing about vim and alternatives feels intuitive or easy to use
(Neo)vim doesn't need to reinvent itself to be more accessible, because it does what it does very well. I'm a web dev and have used vscode like anybody else for a long time. I decided to try neovim because vscode was performing badly, but kept me using it because of how good the developer experience is. Once you learned how to use it, there is just nothing better.
but when every other software with keyboard shortcuts agrees on certain easy to remember standards, I don't quite understand how software that goes against all of that hasn't been replaced or hasn't reinvented itself in newer versions
In a way, it has been replaced. Most people will use a user friendly IDE and ignore vim. The thing about vim is that it does things in a fundamentally different way than any other editor, so reinventing itself would mean loosing everything that makes it good, then you better off using something else.
Then again, I have no idea what the difference between vi, vim, emacs, and nano are
Nano is a simple, easy terminal text editor; vi, vim and neovim are three versions of the same quirky and hard, but very good text editor/IDE; emacs is a quirky, but kinda bad editor that has amazingly good extendability.
Wouldn't you want to just want to type q! As you've probably opened it and accidentally made changes you didn't want to. So you wouldn't want to save the config file. Or the text file you just created.
Ctrl+Alt+F2
reboot
I've never understood people arguing about terminal text editors like nano and vim. Why not just use a GUI text editor like gedit?
I'm not the most Linux savvy but when I ssh onto a work machine I'll use a terminal editor instead of copying the file onto a local machine, editing the file in a GUI and then overwriting the file on the remote machine
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.