To my eyes, nano-1.3.3-r1 emerges with no suspicious errors, but when I go to save a file (ctrl-o), nothing happens. This occurs in both terminal.app and aterm. Pico, which also uses ctrl-o to save, saves fine. Searched nano-editor.org but there didn't seem to be anything relevent, neither on fink. Couldn't check opendarwin because I couldn't find a place to search there lists.
nano-1.2.4 and nano-1.3.2-r1 are unaffected by this bug and I should note compile fine. So please add ~macos to those.
Steps to Reproduce:
1.Try to save a file with ctrl-o.
Doesn't allow saving.
not major, but still annoying
Problem persists in nano-1.3.4
Changing the severity back to major, because like a wagon without wheels, an editor without save... is useless. Back to vim, I guess.
I discovered this one early, and assumed it was localized to my machine when nobody else mentioned it - since then, my workaround has been to use Ctrl-X, then using the save-before-quit feature in lieu of Ctrl-O.
Even still, this is a supremely irritating glitch.
Yeah I've experienced this under FreeBSD as well. One time I got it work, but I am uncertain of what it was that I did. I want to say it worked after I rebuilt w/USE=ncurses but I just can't remember.
Oh, and Trixtrax, just as Paul said, you can indeed save, you just have to Ctrl-X and hit 'y' before exiting.
1.2.4 is the last version I've found to NOT have this problem. If its any consolation, F3 seems to work for me
If this problem is shared between OSX and FreeBSD, this may be related to the GNU vs BSD coreutils. IIRC, this issue occurs even in a straight build (non-Gentoo) which might indicate an issue that needs to be addressed by the nano devs, not Gentoo.
Just emerged nano-1.3.5, Ctrl-O seems to be working on my system. Can anybody confirm?
I confirm Thomas' discovery - ^O works fine in 1.3.5 - what do we need to do to get this keyworded into (~)ppc-macos?
works for me too. Closing this up.
Closing out bugs that've been resolved for a while now...