Team Vim. Because I learned the vim basics once 20 years ago and never bothered to learn after that. :D
I see you and raise straight vi.
That's what I was taught at my first tech internship. It's all they had on the UNIX system running the webserver in 1998.
I did write some web pages the pulled live data from the backend. I had the pleasure of writing them in C. I got the data binding to some kind of CORBA system using extern variables that were bound at compile time. All of the html (no js or css yet) was hand built and generated from the C code.
vi was the only editor on the system and there was no way to use arrow keys (the UNIX system didn't have them on the keyboard at all).
I also had the displeasure of building a backup system on a floppy where I had to write a bat script that could manually load a token ring driver, bind a SMB share, load Ghost backup software and backup the local hard drive at under 2mb (yay coax thicknet). The tool used to query and write through the hostname for the backup? Copycon. Fucking copycon in DOS. That showed me how a terrible (but working) tool could be to work with.
Unless an editor can do reasonable vim emulation, I can't take it seriously. You're welcome to use it, but I won't be able to get anything done in it quickly. The vi keys are too ground into my reflexes.
Vim sorely underrated. Great tools/hotkeys. Felt like a master pianist clacking away while the terminal went berserk until suddenly the 2 hour job was done in 20 minutes.
At the risk of restarting the Editor wars (https://en.wikipedia.org/wiki/Editor_war) from days of yore, I find it interesting that emacs wasn't even in your list of contenders. I hear it mentioned less frequently these days, so perhaps it's going by the wayside?
For the record, I'm a vi/vim user! I had the privilege of being taught to use it by an RFC-writing greybeard decades ago, and have used it without thinking ever since.
For those who find themselves on a machine with only vi/vim, or want to learn, here's a quick primer when editing a file (usually done by typing "vi foo.txt" in a shell) --
:q! ...Force quit vi (:q also works -- gentler!)
:wq! ...Save file and quit vi
i (then type characters) ...insert text at current position
A (then type characters) ...Insert at end of current line
G ...go to first character of last line in the file
/foo ...search for first occurrence of "foo" in the file (hit / again to find additional instances)
x ...Delete character under cursor
:56 ...Go to line 56
yy ...Copy the line the cursor is currently on into the buffer
p ... Paste the buffer
r (then type character) ...Replace character under cursor
u ...undo (hit multiple times to undo prior actions)
When done with a command like this, hit Esc to go back into normal mode.
Second nature after a bit of practice! I used to work with a guy who insisted on using ed. That was... odd.
Yeah but op was comparing editors, not OS's. https://emacsos.dev/
I use Helix... Uhhh idk I think it's nice I guess
There are dozens of us!
micro for sensible defaults out of the box, and because I don't like modal editors.
Neovim
nano for quick things; emacs for longer typing sessions.
Emacs
Team Neovim.
I looked into ed, then decided its not for me.
nano. I can't memorize esoterica.
Nano, because it's the only one I can remember how to quit from without power cycling the computer.
Top Tip: open another terminal and kill the task from there
( /s )
NANO I just need simple, and tell an me how to save and exit without abstract key codes.

I'm an emacs -nw kind of guy.
But if I have to pick one of your options, nano
Emacs.
With all the vimmery going around nowadays though, I feel like I'm on the losing team. ;_;
Join us! Use Evil mode!
Still team Emacs. We're a team because we use elisp, not because of something trivial like how our text editors work.
Vim, but I also find this battle completely stupid.
I use nano because I haven't learned how to use anything else yet.
I use nano because it's always there.
I only ever use a terminal based editor for making quick edits of config files, so nano works just fine for me.
Nano. It's easy and I've never had a reason to change.
vim
Helix
Helix when I can install things, vi when I can't.
vim, mainly cause I haven't figured out how to quit yet.
I use emacs
mcedit
I have switched to using helix, so no matter which distro I am on I need to change it to be my default by setting the EDITOR env var.
"Why are we running from the police, Dad?"
"Because they use vim, son. We use Emacs".
Vim forever, any flavour, don't care.
Why? Does actually exist anything else for the terminal?
I realized that I'd forgotten about pico and joe, the latter was my very first text editor (hated it!).
There are also Helix and Microsoft Edit.
I'm on team "whatever comes pre-installed"
@SocialistVibes01 Emacs of course
Neovim. One time I accidentally opened nano and couldn't figure out how to get out of it... Wtf is with those keybinds?
Lol at emacs not even being on your list. Suck it, emacs users 😂😂❤️
Firstly, Emacs is not an alternative to any terminal based text editor, it's an alternative to the terminal based workflow in general.
Secondly, Emacs users can live without the hype, churn and elitism of the vim ecosystem and with a better editor instead.
Neovim.
Vi
I used to use Neovim but now I mainly use Helix, it's really good by default, the most hassle is usually just looking up an LSP for a language and installing it.
My config file literally only has the theme I use, unlike the heavy configs I'd have to make so that vim/nvim are the way I want. I also like the multiple cursor approach it has to editing.
Just echo text to create a new file or use sed and awk to edit an existing file.
In reality, I use nano for edits and vimdiff for comparing files (usually a .pacnew after an update on a headless device)
Atleast be a neckbeard and use cat the way neckbeard Gods intended \s
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0