Updated for final nano.save behaviour

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@371 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

diff --git a/nano.1 b/nano.1
index 55eeed159051e8474f1e2100e03196ef3ec633cb..e308df753e40489eaba9a51bd20915ab353c8fea 100644 (file)
--- a/nano.1
+++ b/nano.1
@@ -91,8 +91,8 @@ Nano will try to dump the buffer into an emergency file in some cases.
 Mainly, this will happen if Nano recieves a SIGHUP or runs out of
 memory, when it will write the buffer into a file named "nano.save" if the
 buffer didn't have a name already, or will add a ".save" suffix to the
-current finename. Nano will \fBnot\fP follow symbolic links that are not
-owned by the real userid of the process.
+current finename. Nano will \fBnot\fP write this file if a previous one
+exists in the current directory.
 .SH BUGS
 Please send any comments or bug reports to
 .br