ariadne
/
smol
2
1
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated for final nano.save behaviour 

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@371 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
master
Jordi Mallach 2000-12-03 03:15:19 +00:00
parent b998483369
commit d87b34121f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
nano.1
View File

@ -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 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 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 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 current finename. Nano will \fBnot\fP write this file if a previous one
owned by the real userid of the process. exists in the current directory.
.SH BUGS .SH BUGS
Please send any comments or bug reports to Please send any comments or bug reports to
.br .br