Bug 60400 – MacOS - nano-1.3.3-r1 - Can not save (ctrl+o) in nano - plus other two versions compile fine

• Status: VERIFIED FIXED
• Product: Gentoo Linux

[Description Trixtrax 2004-08-15 02:34:04 UTC]

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.  

Reproducible: Always
Steps to Reproduce:
1.Try to save a file with ctrl-o.
2.
3.
Actual Results:  
Doesn't allow saving.

Expected Results:  
Should save.

[Comment 1 Alexander Plank (RETIRED) 2004-08-24 16:35:14 UTC]

not major, but still annoying

[Comment 2 Thomas 2004-10-02 02:42:53 UTC]

Problem persists in nano-1.3.4

[Comment 3 Trixtrax 2004-11-05 01:35:16 UTC]

Changing the severity back to major, because like a wagon without wheels, an editor without save... is useless. Back to vim, I guess.

[Comment 4 Paul Handly 2004-11-06 01:25:06 UTC]

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.

[Comment 5 Aaron Walker (RETIRED) 2004-11-13 17:11:22 UTC]

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.

[Comment 6 Kito (RETIRED) 2004-11-13 17:18:35 UTC]

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

[Comment 7 Paul Handly 2004-11-13 23:37:23 UTC]

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.

[Comment 8 Thomas 2004-11-24 00:29:42 UTC]

Just emerged nano-1.3.5, Ctrl-O seems to be working on my system. Can anybody confirm?

[Comment 9 Paul Handly 2004-11-24 01:47:05 UTC]

I confirm Thomas' discovery - ^O works fine in 1.3.5 - what do we need to do to get this keyworded into (~)ppc-macos?

[Comment 10 Kito (RETIRED) 2004-11-24 09:45:03 UTC]

works for me too. Closing this up.

[Comment 11 Hasan Khalil (RETIRED) 2005-02-06 13:33:12 UTC]

Closing out bugs that've been resolved for a while now...