Nano has already supplanted the great EMacs and Vim as the most popular text editor of all linux distros, for though it has many omissions in functionality it scores over the older, more complete programs in two important respects. First, it is slightly simpler; and secondly it has the text “^ Exit” inscribed in highlighted text on its footer
EDIT : This sees to be going over some people’s heads. It’s a hitchiker’s guide to the galaxy reference.
The Hitchhiker’s Guide has already supplanted the great Encyclopaedia Galactica as the standard repository of all knowledge and wisdom, for though it has many omissions . . . it scores over the older, more pedestrian work in two important respects. First, it is slightly cheaper; and secondly it has the words DON’T PANIC inscribed in large friendly letters on its cover.
That’s because Ubuntu, honestly.
I’ve used Vim, NeoVim, Micro,
mg(1), JOE, and even MS Edit (both the original DOS version and the recent Rust clone). No matter how complex and tailored I wrote my config, though, the features I actually used were included in GNU nano and/or my command shell without any of the bugs, bloat, learning curve, or slop.Using it as my default just makes sense.
Nano is great for editing files. It is absolutely terrible for any amount of text processing or anything other than raw code copied from a tutorial
Best local simple terminal text editor is micro.
It is insane how far using the same shortcuts literally everything else can get you in the world of terminal text editors and yet here we are
oh no, not again.
Sometimes I catch myself opening nano inside emacs’ term. I literally forget I’m using emacs and just do it on instinct. I once also opened emacs inside emacs’ term and I just stared at the screen in disbelief.
Emacs: “Sure, fuck it, why not.”
I’m in the “been working with Linux since the 90s” gang so I call vim vi and nano pico and when I started there was a coolness factor to be considered. I was incredibly uncool so I used whatever I wanted, including pico - I mean you used pine for email back in the day and the interface was nearly identical, so whatever.
But I did want to be at least a tiny bit cooler, so I learned vi in a fairly rudimentary fashion. I can edit, jump, delete, search, replace, copy and paste - oh, and I can exit. I’ve spent so much time using vi, that my brain doesn’t even have to think about exiting, not even whether I want to write or not. It just happens like second nature. It’s actually gotten to where nano seems unduly burdensome to me.
But really, I prefer an IDE for programming. CLI editors will always be for configuration files and shell scripts to me.
It’s there and it’s easy. Most people don’t use terminal text editors unless they are SSHing in a server, and they would only do that sporadically, so it makes no sense to become proficient in a complex text editor like vim or Emacs for that little use case.
Sidenote: personally, I learned vim once, and used it extensively every day for two years. I stopped using it for one year and was back to square one. Now I use vscode for everything… Even when I’m using SSH, because vscode supports SSH
I always forget that vscode can do that
Every editor “supports” SSH, you can mount files on a remote SSH server via SSHFS.
And instead vscode supports SSH (without quotes), you can connect to an SSH host, and it will open files and folders on the host like it does locally. And if you open the integrated terminal it will run on the remote host. And it will forward the git login agent so you can commit or push with the credentials of your local machine. And it can forward ports from the remote.
It’s kind of sad that many people don’t use the shell / terminal anymore, especially as part of their regular development flow. There’s so much scripting and so many shell commands you can use that will do things you just can’t do in vscode. And having an editor like vi immediately available is part of that flow.
For me, vim and the shell are my primary IDE. I rarely fire up vscode. But I guess I’m getting old. Still faster than the younger devs who mainly use vscode and then struggle when they are forced to use the command line due to whatever circumstance where vscode is not available or appropriate. Kind of makes me sad. Feels like a valuable skill is being lost.
Oh, I use the terminal a lot, it doesn’t throw me off. When I can’t have vscode (e.g. small openwrt devices) I can use vim. It’s just plain easier to use vscode for editing files when I can
I only use terminal text editors anymore when I need to edit config files à la
sudo nano. I just don’t trust visual text editors to do that stuff, I’ve been burned too many times in the past. Files “saving” but not actually saving. Files actually corrupting or changing ownership on save. Etc. Good old nano, doesn’t fuck with the critical system files any more than I already am.
Not long ago, I needed to quickly add a 4-line thing to my Ruby on Rails app on my Raspberry Pi. I was like, shit, I really can’t be arsed to mount the RPi over Samba to edit this stuff on VSCode on my Windows laptop to add like 4 lines. I don’t have vim, I can’t be arsed to check which vimlike I have at hand, I can’t be arsed to see if my Emacs setup has been customised for this RPi. So fuck it, Nano it is!
The Venn diagram of nano users and Debian/Ubuntu users is a circle
yep. One of the reasons I stick to debian based (vanilla Deb) is so that any dumbass tutorial works for me, because I am not smart.
sample size of me supports this hypothesis
People don’t have to look up “how to exit nano”
Same reason people use notepad on windows. It’s already installed on almost every distro
I have been around since production servers were predominantly HP-UX, Solaris, and AIX. I settled on Vi because it was the one common editor that was preinstalled on every *NIX OS, including Linux and you could jump right into edit mode while reading a file without having to exit the preview first.
Nano is fine, but one you’ve gone through the pain of committing Vi to muscle memory, there’s no point to switch.
I’m part of the “learned Linux when I got my first raspberry pi” gang, and all Ras pi tutorials tell you to use nano. So yes.
I think Vim is great if you use it everyday and know it inside out. For those of us who don’t, Nano is just easier, not least because it tells you in the UI how to exit it xD
It is preinstalled and does what it needs to do. What else can I ask for?
