Vim is built different
-
If you're just doing a quick config edit, nano is significantly easier to use and is also present in most distros.
Vi/Vim is useful as a customizable dev environment, but in the present there are better, more feature-rich development tools - unless you are specifically doing a lot of development in a GUI-free system, for some reason.
What editor is more feature-rich then vim? Out the box it is lacking some sane config but it is one of the more powerful and flexible editors out there - more then a rival for any modern IDE.
-
What editor is more feature-rich then vim? Out the box it is lacking some sane config but it is one of the more powerful and flexible editors out there - more then a rival for any modern IDE.
emacs
-
Clearly you should install Edit.
Classic DOS editor for text files, batch coding, and QBasic coding. Good times.
-
I've recently started administering windows headless. PowerShell over SSH.
Don't have this problem on windows server!
It doesn't even have a terminal text editor
I have to install nano or use powershell commands through hoops of fire just to edit a line in a file.
Or download the file via scp, edit and reupload.
Pure Insanity.
Is edlin still around?
-
emacs
I said editor, not an OS that lacks a decent editor
-
Many people do this.
Many people are insane.
wait till you see emacs, and dont even let me mention vscode that thing runs on JS!
-
If you're just doing a quick config edit, nano is significantly easier to use and is also present in most distros.
Vi/Vim is useful as a customizable dev environment, but in the present there are better, more feature-rich development tools - unless you are specifically doing a lot of development in a GUI-free system, for some reason.
vim is more feature rich than nano, nano is easier to use for the first time, after you learn the very basics vim is pretty much just as easy to use and way more feature rich
-
My actual issue is I need approval to install anything on any server. This might get approved since it's MS though! Thanks.
I think they plan on making it ship with windows by default at some point, so perhaps it'll be in future versions of Windows Server and you won't have to add it.
-
How about :x.
how about alt+printscreen lift printscreen but keep holding alt, now press b, you succesfully exited vim, works for emacs too!
-
I've used vim, and I didn't like it. That is the definition of an opinion.
wrote on last edited by [email protected]“I didn’t like it” is an opinion. “Vim is dumb because I can’t think of a reason people would like it, and everyone who uses it is an elitist asshole” is ignorance.
-
:w= write; or overwrite if the file already exists.Please don’t give blanket destructive advice.
This one's fine. They'll then learn the next vim button, u for undo. I believe it's saved between boots of vim? It may be my kickstarted neovim config tho
-
This post did not contain any content.
-
‘vimtutor’ is your friend. Nobody sane uses vim as an IDE, but if you have to ssh to a host to fuck with a config file it’s pretty nice to know because you can guarantee that most distros have at least vi, if not vim.
If using vim makes people insane, then what does using ed makes me?
-
how about alt+printscreen lift printscreen but keep holding alt, now press b, you succesfully exited vim, works for emacs too!
How about
-
Because they grew up with it? I cant think of any other reason. I used it in college for a class bcz my old as fuck professor required it. Its obtuse, old, and doesn't have a lot of functionality of modern code editors.
The only people who want to use it are people who started with it decades ago, or people who were forced to use it, and now think they're superior somehow to everyone else who doesn't use it.
I was also forced to use it at uni (a few decades ago), but didn't start using it until professionally until several years into my dev career. I promise that I don't think I'm superior because I use it. But I do encourage junior developers to learn it for reasons that appealed to me.
Among other things, appealing things are modal editing (the biggest advantage IMO), it runs on pretty much on any server you will be ssh'ing into, less IDE lock in. And, there's a bunch of additional things that other editors do that I think Vim does better: regex is first class in the environment, extensible workflows, macros. Then there are definite advantages being able to quickly navigate from the home row.
I agree that some people will demonstrate their enthusiasm by bragging and being pretentious. But I don't think that's why they stick with Vim.
-
If using vim makes people insane, then what does using ed makes me?
A wizard.
-
This one's fine. They'll then learn the next vim button, u for undo. I believe it's saved between boots of vim? It may be my kickstarted neovim config tho
I would say not in all installations, no. And honestly, it’s not worth trusting.
And for those who are unfamiliar, and want to set it up: https://blog.openreplay.com/persistent-undo-vim-save-restore-history/
-
Im completely lost on Nano. Vim is SO much quicker.
One +ive for
nanois that it has general commands listed down below, by default.
So, as long as you understand^andM-, which you are expected to (idk why, ask sbd else), if you have been using Linux CLI, you will at least know how to exit.Oh, and I just realised: it also says "[ Welcome to nano. For basic help, type Ctrl+G. ]", where it explains what
^andM-are.So
nanocould be considered an accessibility program for people who are new to the GeNerally Used CLI, whilevimis the thing you will configure for yourself when you know what you want.
Oh and I am definitely configuring it. I hate thehjklfor movement. I have arrow keys and I am going to use them. And I am not buying your 60% mechanicals no matter how much you make sure that 100% keyboards are not available with good keys. -
One +ive for
nanois that it has general commands listed down below, by default.
So, as long as you understand^andM-, which you are expected to (idk why, ask sbd else), if you have been using Linux CLI, you will at least know how to exit.Oh, and I just realised: it also says "[ Welcome to nano. For basic help, type Ctrl+G. ]", where it explains what
^andM-are.So
nanocould be considered an accessibility program for people who are new to the GeNerally Used CLI, whilevimis the thing you will configure for yourself when you know what you want.
Oh and I am definitely configuring it. I hate thehjklfor movement. I have arrow keys and I am going to use them. And I am not buying your 60% mechanicals no matter how much you make sure that 100% keyboards are not available with good keys.Agree with your point on nano. I used it as a beginner too, but once you get past the basic typing something in, vim is king.
However, I disagree with the rest of your post. Hjkl are superior to arrow keys once you get used to them. I thought that day would never come, but I got used to it way quicker than initially anticipated.
As a 60% owner and 34 key ergo advocator, also disagree with the last point.
-
This post did not contain any content.
An old Buffalo NAS box made me learn vi. Because that's all it had.
Yes, this comic speaks to me.
