Sat 21 Aug 2010 08:34:44 AM UTC, comment #2:
Hi, I'm the original poster. If there is something (reasonable) I could do to test / reproduce the issue for you, let me know.
(I would have logged in, but even after registering and following the confirmation link via email it won't let me, saying: "Error Account Pending." Lovely.)
|
Tue 17 Aug 2010 05:34:24 PM UTC, comment #1:
Hello,
Hmm, well since this is submitted by None I'm worried I won't be able to get any detailed reproduction info, but if the OP comes back to check on this bug if (s)he could mention whether nano thought the write was successful or not that would be helpful. Actually 2.0.9 added a fix specifically for the case of a full filesystem, but perhaps the writeout (^O) code is doing something different from the exit-time saving code. Thanks for the report either way and apologies for any hardship this may have caused you.
|
Mon 16 Aug 2010 09:41:33 AM UTC, original submission:
Recently I logged into a system to see what had gone wrong with it. I assumed it was a missing setting in a config file I'd forgotten to add.
Unbeknownst to me, the disk/device was actually full, and when I went to save (CTRL+O, S) the config file, it wiped out all the existing data(!!!). The file was still there, but at 0 bytes in size.
FWIW, this is on CentOS 5.5 running 2.0.9:
$ nano -V
GNU nano version 2.0.9 (compiled 10:27:02, Mar 30 2009)
(C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007
Free Software Foundation, Inc.
Email: -unavailable- Web: http://www.nano-editor.org/
Compiled options: --disable-wrapping-as-root --enable-color --enable-extra --enable-multibuffer --enable-nanorc --enable-utf8
|