vim, because that's how my father taught me, and how his father's father taught him.
Choose vim! The generational trauma of file editors!
vim, because that's how my father taught me, and how his father's father taught him.
Choose vim! The generational trauma of file editors!
As a new Linux user who spends as little time editing config files as I can manage, I'm fine with nano.
I was too untilI switched to opensuse aeon and default is vim instead of nano. I just switched. I don't care. Both are not perfect - i won' create yet another fork just because i want to do it differently. I don't get why vim has so few shortcuts.
I donโt get why vim has so few shortcuts.

I was playing around with Free BSD I think and the default was Vi. I was just like "yeah, no" and gave up. I didn't have wi-fi working so I couldn't install anything else.
Came here to say kate! I tried a bunch of them before but kate is nice :3. And then I have nano for the terminal
It has a few quirks I utterly despise :(
Like it cannot print invisible characters. Had a script create some broken folders with a BOM character at the beginning. I couldn't access the files in any way except that they appeared in dolphin and ls. Had to delete them via the fucking inode.
I was forced to use VSCode (an open source fork at least) to find out what the fuck was wrong with the input file the script used to generate the folder name.
Like it cannot print invisible characters.
I was looking at an option to display invisible characters in Kate like last week. So it got better, I guess.
Me no love nano, me brain only can use nano.
E macs scary. vim no let me leave :(
You might like micro :) its like nano but with more user friendly features like Ctrl+s for save, and clicking places to change cursor location. I think you have to enable the "cheat sheet" of keyboard commands being visible all the time if you want it to always be showing like I do
It also supports extensions but I don't really care about that lol. I just want something simple with nice ux :)
p sure latest nano can do all that, you can atleast change the default save bindings to ctrl s in the .nanorc file and im p sure most distros include a build of nano that has mouse support. If its supported by the build, its just a settings toggle in the rc file likr the bindings :)
Micro also has syntax highlighting, multiple buffers with split editors, and theming, among other things. It's pretty dang neat
Why would you need a text editor when you can just do cat > file ?
smh
This command will literally overwrite the file that you do whenever you try to edit it. You need two >> to append at the end of a file, but it's super-duper hard to put text in the middle of a file from the terminal. That is why people use editors, for sure. Now that I think about it, there probably is some psychopath who uses the actual command line as an editor. They're probably more elitist than Vim users lol.
Sounds like a skill issue tbh
Excuse me, but real programmers use butterflies.
Thinking out loud here. Head in a temp file, cat, tail the rest and then overwrite?
Let the editor holy wars (re)start!
Vim is the one true editor, and the heretics who claim otherwise shall be driven forth and sent to re-education linux boot camps to learn the true ways.
I've only ever seen vim users call for holy wars.. I'm happy with my RSI and carpal tunnel syndrome. Emacs till death do me fart.
ed is the standard editor
My requirements for a text editor:
Bonus points if it comes pre installed.
I use Micro in the terminal - it offers good desktop integration with keys similar to DEs like ctrl+v and ctrl+c, rather than being terminal centred (e.g. Ctrl+C is usually the standard interrupt/abort key in the terminal). So it's nice if you're mainly in a desktop but pop in to a terminal occasionally and have the DE muscle memory.
I use Kate outside the terminal.
But honestly, which text editor you use depends on what you use it for and how often. Vim is very powerful and allows very fast use & productivity if you learn it properly and probably very useful if you spend a lot of time in the terminal or TTY, but Nano is more straight forward and easy for a lot of basic terminal based work.
I'd look into Fresh if you want to really have the whole gui-style text editor experience inside a TUI application.
The so-called desktop integration is what I disable in vim. I want to have the terminal in control and use select text to copy instead of entering visual mode. When I want visual mode, I use my keyboard. (:
I'm a emacs guy, but nano should be the only one installed by default. The default editor should tell you how to exit!
Not our fault everyone blows past the kind offer of : vimtutor on startup! (I kid. The default editor shouldn't require a class.)
You're 100% correct. Nano is a perfectly reasonable default.
That said, it is 2026. It also wouldn't kill us to default to an interactive one-time prompt that defaults to nano, but offers one or two others, and removes itself after setting the user's choice.
vi because it's everywhere, even on servers where packages can't be downloaded or shouldn't be installed.
This is my reply every time someone suggests nvim. Is it on the servers I use but I'm not an admin for? No? Then it doesn't sound like a great option.
Nano because I'm too lazy to learn vim or emacs. I want something that works and not something that operates like cheat codes in old video games.
First choice: use a normal damn GUI text editor
Second choice: Nano. It's simple and comprehensible, and a best CLI choice for newbies. You can then turn to vim, emacs, or whatever, but don't make your life harder from the get-go
People suggesting to start with Vim are probably the same ones pushing for Arch as a first distro. C'mon.
Thatโs how you breed scrubs who canโt M-x-butterfly. I say give them a distro that boots into vi and starts a background process that block internet access around them. If they manage to quit vi and kill the daemon, theyโre ready for Linux.
Was gonna write that only one true text editor exists. But okay, you are right, of course

Nothing wrong with Kate. I know how to use Nano because it's an essential skill for when your machine boots into emergency mode, but aside from that editing text from the terminal is lunacy.
ed is the standard text editor.
Even worse: I like GUI editors like Kate/KDevelop/Geany/VSCode. Unless it is on a server obviously.
I don't understand the issue. I've been using Linux less than a year but I started with a KDE desktop so it came with Kate, Kwrite, and Nano. I've literally never needed anything else.
I've tried out a couple IDEs like Codium and Geany, but I don't see what they offer that Kate doesn't.
I've also at least opened Emacs but I didn't get much further than that.
I use Nano in the terminal when I'm editing config files because I read somewhere that it's safer.
I installed Neovim and Micro but I haven't explored those at all yet. I don't have any problems with Nano.
I tried Pluma but I really only use it for dumping lists.
For the most part I use Kate, but for simpler notes I use Kwrite just to keep them in separate spots on my launcher.
I don't see why this is such an issue though.
All I'm gonna say is than nano is installed on almost every Linux os and has the keyboard shortcuts written on the UI.
Who doesn't have vi/m?
Fwiw, helix also gives visual feedback on bindings if a key is a table for mutiple bindings.
I'm sorry I don't see how that's relevant to my point.
I'm saying that of all the text editors, nano is the one that usually takes the least amount of effort to learn and set up. Both of those options require either learning or set up, so why would I choose them if convinience is what I'm after?
I was just asking which distros don't have vi/m. The helix point was an aside. It wasn't combative, just curious.
i am quite fond of kate
Wait until you get cornered by elite Helix enjoyers
Helix is very enjoyable to use
For now. Soon it'll be plugin slopped.
I already use it without plugins (since it doesn't support them). Why wouldn't I just not install the plugins?
That's not the issue so much as it leads to the collapse of serious development. Better put, if these plugins are so important, why not add them to the editor? Instead we get turing complete configuration and all the performance degradation downstream of it.
I use Vim, which has some really handy tricks that I use somewhat often (eg, type :r! followed by a terminal command and it will add the standard output of said command to the bottom of your file).
That being said, there's nothing wrong with Nano. Most distros come with it out of the box nowadays, and its learning curve is practically nonexistent compared to the alternatives.
mcedit๐
This is kinda irrelevant for a new user, but vi/vim is available literally everywhere. If you need to shh onto another machine and edit some files, it's the only editor you can reliably expect to exist.
Best choice: use whatever comes pre-installed.
I learned vim (technically vi) because it was the only editor available on these tiny liveusbs I would use for work. It was literally my only option. Once I got used to the motions, using any text editor without vim motions felt unusable to me.
Commit heresy with evil-mode Emacs.
top 99 comments