GNU nano is a nice easy text editor… but it’s so clunky when you have become comfortable with vim (perhaps the same with Emacs).
The trick is to never get comfortable with Vim or Emacs.
*taps forehead*
I think nano is good for quick and dirty editing.
Anything else should be done locally on your development machine with a GUI, then pushed to your server as an update.
Why insist on a GUI for anything else?
apt purge nanois one of the first things I do on a new Debian installation. Much easier to remember than having to useupdate-alternatives,select-editorand the$EDITORvariable to convince the likes ofvigr,vipw,visudo,crontab -e,… that I really want to use vim as my primary editor.Honestly unreasonably infuriates me when I enter
visudoand find myself innano… Like, did I typenanosudo? Hell no!
Also worth checking out helix editor. Once you do the tutorial it makes vim feel clunky
Lol I wasn’t aware that nano is actually a GNU project. Checking the date on Wikipedia when it became one really threw me off today morning: 2001. Man I was living behind the moon and could not exit properly the entire time!
I remember using Pico, Nano’s predecessor, in the mid-to-late '90s. Nano was created because there was a desire to distribute Pico with Linux. Unfortunately, the licensing was unclear so a clone had to be made. Fortunately there was no argument about editor appearance and behaviour.
As shocking as the 2001 date might be, it seems like Pico might have ceased development as recently as the end of 2022 along with its e-mail reader parent program Alpine (formerly Pine).
If true, Nano still has a few years to go before it will overtake its parent for longevity.
(Both vi and Emacs are far older, of course.)
deleted by creator
Annoys me that “modern” in this case means whatever Microsoft does and whatever Microsoft users are used to. Especially since a lot of those “modern” binding have been around since the 80s.
“Modern” has become one of those words that’s way over used to the point of meaninglessness.
vim > all
