update.

[chise/xemacs-chise.git-] / man / lispref / backups.texi

diff --git a/man/lispref/backups.texi b/man/lispref/backups.texi
index 59aa856..cac8e56 100644 (file)
--- a/man/lispref/backups.texi
+++ b/man/lispref/backups.texi
@@ -1,6 +1,6 @@
 @c -*-texinfo-*-
 @c This is part of the XEmacs Lisp Reference Manual.
 @c -*-texinfo-*-
 @c This is part of the XEmacs Lisp Reference Manual.

-@c Copyright (C) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc. 
+@c Copyright (C) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc.

 @c See the file lispref.texi for copying conditions.
 @setfilename ../../info/backups.info
 @node Backups and Auto-Saving, Buffers, Files, Top
 @c See the file lispref.texi for copying conditions.
 @setfilename ../../info/backups.info
 @node Backups and Auto-Saving, Buffers, Files, Top

@@ -78,9 +78,9 @@ which may save disk space.  (You would put this code in your
 
 @smallexample
 @group
 
 @smallexample
 @group

-(add-hook 'rmail-mode-hook 
+(add-hook 'rmail-mode-hook

           (function (lambda ()
           (function (lambda ()

-                      (make-local-variable 
+                      (make-local-variable

                        'make-backup-files)
                       (setq make-backup-files nil))))
 @end group
                        'make-backup-files)
                       (setq make-backup-files nil))))
 @end group

@@ -121,7 +121,7 @@ its value.  Major modes should not set this variable---they should set
 @subsection Backup by Renaming or by Copying?
 @cindex backup files, how to make them
 
 @subsection Backup by Renaming or by Copying?
 @cindex backup files, how to make them
 

-  There are two ways that XEmacs can make a backup file: 
+  There are two ways that XEmacs can make a backup file:

 
 @itemize @bullet
 @item
 
 @itemize @bullet
 @item

@@ -226,7 +226,7 @@ backup version 3 is excess.  The function @code{find-backup-file-name}
 (@pxref{Backup Names}) is responsible for determining which backup
 versions to delete, but does not delete them itself.
 
 (@pxref{Backup Names}) is responsible for determining which backup
 versions to delete, but does not delete them itself.
 

-@defopt trim-versions-without-asking
+@defopt delete-old-versions

 If this variable is non-@code{nil}, then saving a file deletes excess
 backup versions silently.  Otherwise, it asks the user whether to delete
 them.
 If this variable is non-@code{nil}, then saving a file deletes excess
 backup versions silently.  Otherwise, it asks the user whether to delete
 them.

@@ -347,7 +347,7 @@ This function returns the name of the most recent backup file for
 
 Some file comparison commands use this function so that they can
 automatically compare a file with its most recent backup.
 
 Some file comparison commands use this function so that they can
 automatically compare a file with its most recent backup.

-@end defun 
+@end defun

 
 @node Auto-Saving
 @section Auto-Saving
 
 @node Auto-Saving
 @section Auto-Saving

@@ -357,10 +357,10 @@ automatically compare a file with its most recent backup.
 called @dfn{auto-saving}.  Auto-saving prevents you from losing more
 than a limited amount of work if the system crashes.  By default,
 auto-saves happen every 300 keystrokes, or after around 30 seconds of
 called @dfn{auto-saving}.  Auto-saving prevents you from losing more
 than a limited amount of work if the system crashes.  By default,
 auto-saves happen every 300 keystrokes, or after around 30 seconds of

-idle time.  @xref{Auto-Save, Auto-Save, Auto-Saving: Protection Against
-Disasters, emacs, The XEmacs Reference Manual}, for information on auto-save
-for users.  Here we describe the functions used to implement auto-saving
-and the variables that control them.
+idle time.  @xref{Auto Save, Auto-Save, Auto-Saving: Protection Against
+Disasters, xemacs, The XEmacs User's Manual}, for information on
+auto-save for users.  Here we describe the functions used to implement
+auto-saving and the variables that control them.

 
 @defvar buffer-auto-save-file-name
 This buffer-local variable is the name of the file used for
 
 @defvar buffer-auto-save-file-name
 This buffer-local variable is the name of the file used for

@@ -421,7 +421,7 @@ be sure to redefine the function @code{make-auto-save-file-name}
 correspondingly.
 @end defun
 
 correspondingly.
 @end defun
 

-@defun make-auto-save-file-name
+@defun make-auto-save-file-name &optional filename

 This function returns the file name to use for auto-saving the current
 buffer.  This is just the file name with hash marks (@samp{#}) appended
 and prepended to it.  This function does not look at the variable
 This function returns the file name to use for auto-saving the current
 buffer.  This is just the file name with hash marks (@samp{#}) appended
 and prepended to it.  This function does not look at the variable

@@ -579,9 +579,9 @@ name.
   If you have made extensive changes to a file and then change your mind
 about them, you can get rid of them by reading in the previous version
 of the file with the @code{revert-buffer} command.  @xref{Reverting, ,
   If you have made extensive changes to a file and then change your mind
 about them, you can get rid of them by reading in the previous version
 of the file with the @code{revert-buffer} command.  @xref{Reverting, ,

-Reverting a Buffer, emacs, The XEmacs Reference Manual}.
+Reverting a Buffer, xemacs, The XEmacs User's Manual}.

 
 

-@deffn Command revert-buffer &optional check-auto-save noconfirm
+@deffn Command revert-buffer &optional check-auto-save noconfirm preserve-modes

 This command replaces the buffer text with the text of the visited
 file on disk.  This action undoes all changes since the file was visited
 or saved.
 This command replaces the buffer text with the text of the visited
 file on disk.  This action undoes all changes since the file was visited
 or saved.

@@ -597,6 +597,10 @@ Normally, @code{revert-buffer} asks for confirmation before it changes
 the buffer; but if the argument @var{noconfirm} is non-@code{nil},
 @code{revert-buffer} does not ask for confirmation.
 
 the buffer; but if the argument @var{noconfirm} is non-@code{nil},
 @code{revert-buffer} does not ask for confirmation.
 

+Optional third argument @var{preserve-modes} non-@code{nil} means don't
+alter the files modes.  Normally we reinitialize them using
+@code{normal-mode}.
+

 Reverting tries to preserve marker positions in the buffer by using the
 replacement feature of @code{insert-file-contents}.  If the buffer
 contents and the file contents are identical before the revert
 Reverting tries to preserve marker positions in the buffer by using the
 replacement feature of @code{insert-file-contents}.  If the buffer
 contents and the file contents are identical before the revert