commit d87b34121f0a4f745273bdb99c54b6c9d9d586cb
parent b99848336970ed920d3e54ca99c3e3b5b9a607f4
Author: Jordi Mallach <jordi@gnu.org>
Date: Sun, 3 Dec 2000 03:15:19 +0000
Updated for final nano.save behaviour
git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@371 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
Diffstat:
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git 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
