This is good news: It's also good to actually see RMS actually compromising.<p>Also, nano is actually a useful tool, despite its reputation as the editor for those who don't know what they're doing. It's an excellent editor for quick edits that aren't worth pulling up emacs for. Although I would never reccomend it for Real Work, that's not really its intent. And it owns its field, having crushed all competition save vi, which is really in its own class.<p>Also, nano is frankly a lot more powerful than a lot of people give it credit for: It's just not programmable, which is a necessity in editors these days.
Good to hear. Nano's up-front display of the core key combinations has been a source of relief for people getting dropped into a terminal editor for ages. Wish more distributions would set nano as the default $EDITOR instead of vim.
Happy to see the conflict settled! Here's what's in the news entry for the GNU release:<p><pre><code> With this release we return to GNU. For just a little while
we dreamt we were tigers. But we are back in the herd,
back to a healthy diet of fresh green free grass.</code></pre>
Anybody else use ed(1)?<p>My main editor is acme, and when I need to do large edit jobs on remote servers I control I use sam. However, when I have to edit files on servers I don't control, or when I have to do a quick edit job and I don't have a sam terminal started yet, I use ed.<p>Unlike all other editors, ed doesn't erase the screen. I find this extremely useful. Also, ed is always the same. Vi is not always the same on different systems. Sometimes it has syntax syntax highlighting by default, forcing me to make effort to turn it off, sometimes nocompatible is set on or off, etc.<p>Ed is always the same and has no settings.<p>Sometimes inside my acme session I run win(1), and sometimes in my win sessions I ssh to some system and run ed inside acme.<p>I forced myself to use ed exclusively for a week some years back, and since then I stuck with it.
It's a great editor, I use it all the time with new Raspberry Pi people. Since it's so simple to use we can focus on what we are doing vs learning on how to drive an editor.<p>Happy to see RMS was willing to compromise and keep nano in the hurd.
Context: <a href="https://news.ycombinator.com/item?id=11953044" rel="nofollow">https://news.ycombinator.com/item?id=11953044</a><p>See also, if you have time to read:
<a href="https://www.reddit.com/r/linux/comments/4p9n7e/as_of_nano_260_its_no_longer_a_gnu_project/" rel="nofollow">https://www.reddit.com/r/linux/comments/4p9n7e/as_of_nano_26...</a>
To be honest, I didn't realise that nano was being maintained, I sort of assumed that it was slowly fading out of existence. Honest question: does anyone here use nano for anything? If so - what are you reasons for using it / what do you like about it?
The previous HN discussion for some context: <a href="https://news.ycombinator.com/item?id=11953044" rel="nofollow">https://news.ycombinator.com/item?id=11953044</a>