From d87b34121f0a4f745273bdb99c54b6c9d9d586cb Mon Sep 17 00:00:00 2001 From: Jordi Mallach Date: Sun, 3 Dec 2000 03:15:19 +0000 Subject: [PATCH] Updated for final nano.save behaviour git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@371 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- nano.1 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nano.1 b/nano.1 index 55eeed15..e308df75 100644 --- 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 -- 2.39.5