summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2024-05-21 15:34:50 +0300
committerEli Zaretskii <eliz@gnu.org>2024-05-21 15:34:50 +0300
commit5ab144c77cda1d56f0dd62606c316c712a0d2563 (patch)
tree1589c56aabdea62056f6dafd1877a94f29690941
parenta4828155d8f2b5dc379dd20f17cb478b63425b64 (diff)
downloademacs-5ab144c77cda1d56f0dd62606c316c712a0d2563.tar.gz
emacs-5ab144c77cda1d56f0dd62606c316c712a0d2563.tar.bz2
emacs-5ab144c77cda1d56f0dd62606c316c712a0d2563.zip
; Improve documentation of backing up files
* doc/emacs/files.texi (Backup Copying): Mention that 'backup-by-copying' is safer. Document 'file-precious-flag'. (Bug#71074)
-rw-r--r--doc/emacs/files.texi8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
index 393c4728422..01d22564f2e 100644
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -786,6 +786,14 @@ those previous versions. If you want to be able to do that with files
hosted by those services when editing them with Emacs, customize
@code{backup-by-copying} to a non-@code{nil} value.
+@vindex file-precious-flag
+ Copying the old file for backup is also useful when editing precious
+files, because it makes sure the old file keeps its name if something
+fails between the backup and the saving of your edits. Alternatively,
+you can customize @code{file-precious-flag} to a non-@code{nil} value,
+which implies backups by copying and also protects against I/O errors
+while saving your edits.
+
@node Customize Save
@subsection Customizing Saving of Files