procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Remove unnecessary ref to coreutils manual

Browse source 
* doc/lispref/files.texi: Document write-region-inhibit-fsync.
This commit is contained in:
Paul Eggert 2016-09-11 15:09:04 -07:00
parent c417f08b16
commit 073048d5de
1 changed files with 14 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/lispref/files.texi
View file

@ -661,6 +661,15 @@ feature is useful for programs that use files for internal purposes,
files that the user does not need to know about. files that the user does not need to know about.
@end deffn @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{} @defmac with-temp-file file body@dots{}
@anchor{Definition of with-temp-file} @anchor{Definition of with-temp-file}
The @code{with-temp-file} macro evaluates the @var{body} forms with a The @code{with-temp-file} macro evaluates the @var{body} forms with a
@ -1812,12 +1821,15 @@ copy on secondary storage is lost due to media failure. Second, the
operating system might not write data to secondary storage operating system might not write data to secondary storage
immediately, which will lose the data if power is lost. 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 Although both sorts of failures can largely be avoided by a suitably
configured file system, such systems are typically more expensive or configured file system, such systems are typically more expensive or
less efficient. In more-typical systems, to survive media failure you less efficient. In more-typical systems, to survive media failure you
can copy the file to a different device, and to survive a power can copy the file to a different device, and to survive a power
failure you can invoke the @command{sync} utility (@pxref{sync failure you can use the @code{write-region} function with the
invocation,,, coreutils, The @sc{gnu} @code{Coreutils} Manual}). @code{write-region-inhibit-fsync} variable set to @code{nil}.
@xref{Writing to Files}.
@node File Names @node File Names
@section File Names @section File Names