Every time a distro defaults my editor to nano, I lose a brain cell. Why, why this crappy abomination of an editor? Distro maintainers, default to proper vim for an editor like real men! Fucking hell!

Or even better, neovim

@irene easier said than done when new systems pop into existence more quickly than I change my underwear :')
I am looking into automating deployments though. Hopefully that'll alleviate at least some of the issues with configuration defaults.

#kakoune for all

Because check how many hits has got stack overflow how to exit vim. Speaks volume. If you know vim you know how to change the default. Stop whining and be a man!

Real men don't cry like a baby for their milk.

My god and saviour, nano.

I love nano. It's easy to use and gets the job done.
All I need on the command line is a super basic text editor. vi or vim is too much hassle and not worth the time imo.

Because what is default config for? Common use and especially for little things like this that everyone will change as he likes: for new user that don't already know how to change it.

And what append when a new user which is not born in the linux universe first interact with vim alone? Ragequit...

nano is awesome.
nano is awesome.
nano is awesome.
nano is awesome.
nano is awesome.

(Read in WWE fans chanting flow)

I used pico at first, because it was the default editor for pine, and that was how we were taught at freshman orientation to get our email when I started college in 1996. Our email server ran AIX. I liked pico and pine very much, but by the time I had my first job in February 2001, I decided that I needed to learn vi, so I sat down at one of the HP-UX workstations in the control room one night and went through vimtutor. In 15 minutes, I was 100% hooked. I LOVED it, and I haven't looked back. After that, instead of pine, I used mutt for email, with vim as the editor.

Some time in the early 2000s, the open source community overtook the Unix community in terms of users, and pico's relatively onerous license prompted the community to replace it with nano, a functionality identical editor with better licensing terms. By that time though, I was far too invested in the speed, functionality, flexibility, and power of vim to ever have any more use of nano than exclaiming, "God dammit!" when it would come up when I typed vipw, vigr, or visudo.

@bahua my thoughts exactly! This particular container was actually an Ubuntu one I was just setting up, also with visudo to add sudo access for some users (good thing that apparently their sudoers allow groups sudo and admin by default, so I just had to usermod them in). But I mean it's literally in the name even. Vi-sudo, not na-sudo. Actually wouldn't it be possible to please everyone by making a visudo that defaults to vi/vim and nasudo that defaults to nano?

@sjzurek @ddephor as I've touched on before, I wouldn't whine over a single host because frankly I couldn't care less about configuring one machine. Even if it costs me a full weekend which Arch and co. usually do. Things change however when you have to do it on a dozen hosts and counting, on a regular basis. As said before as well, I am fixing this as it really stems from a bigger issue - a lack of maintenance and deployment automation.

sudo ln -s /usr/bin/vim /bin/nano. Problem solved :P

i use nano to write code and vim to wipe my ass

nano is love
nano is life