From a2ce6f5da40e6b19e293588f2872a9fdb06b9bb1 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sun, 11 Sep 2016 15:09:04 -0700 Subject: [PATCH] Remove unnecessary ref to coreutils manual * doc/lispref/files.texi: Document write-region-inhibit-fsync. --- doc/lispref/files.texi | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/doc/lispref/files.texi b/doc/lispref/files.texi index b912d7b..9a56d0a 100644 --- a/doc/lispref/files.texi +++ b/doc/lispref/files.texi @@ -661,6 +661,15 @@ Writing to Files files that the user does not need to know about. @end deffn +@defvar write-region-inhibit-fsync +If this variable's value is @code{nil}, @code{write-region} uses the +@code{fsync} system call after writing a file. Although this slows +Emacs down, it lessens the risk of data loss after power failure. If +the value is @code{t}, Emacs does not use @code{fsync}. The default +value is @code{nil} when Emacs is interactive, and @code{t} when Emacs +runs in batch mode. @xref{Files and Storage}. +@end defvar + @defmac with-temp-file file body@dots{} @anchor{Definition of with-temp-file} The @code{with-temp-file} macro evaluates the @var{body} forms with a @@ -1812,12 +1821,15 @@ Files and Storage operating system might not write data to secondary storage immediately, which will lose the data if power is lost. +@findex write-region +@vindex write-region-inhibit-fsync Although both sorts of failures can largely be avoided by a suitably configured file system, such systems are typically more expensive or less efficient. In more-typical systems, to survive media failure you can copy the file to a different device, and to survive a power -failure you can invoke the @command{sync} utility (@pxref{sync -invocation,,, coreutils, The @sc{gnu} @code{Coreutils} Manual}). +failure you can use the @code{write-region} function with the +@code{write-region-inhibit-fsync} variable set to @code{nil}. +@xref{Writing to Files}. @node File Names @section File Names -- 2.7.4