[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#60474: 30.0.50; `write-region-inhibit-fsync' and copy-on-write file
From: |
Eli Zaretskii |
Subject: |
bug#60474: 30.0.50; `write-region-inhibit-fsync' and copy-on-write file systems |
Date: |
Mon, 02 Jan 2023 14:12:52 +0200 |
> Date: Sun, 1 Jan 2023 19:21:20 -0800
> Cc: 60474@debbugs.gnu.org, orgmode@tec.tecosaur.net,
> Ihor Radchenko <yantar92@posteo.net>
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> > Paul, any comments?
>
> Sure, Emacs should do the reverse of what it's doing now. That is, Emacs
> should use fsync only in special situations, instead of avoiding it only
> in special situations. In the old days it may have made sense to use
> fsync, but nowadays most platforms don't need fsync for the sorts of
> things people use interactive Emacs.
>
> For what it's worth I've had (setq write-region-inhibit-fsync t) in my
> init file for many years, without problems.
>
> Proposed patch attached.
Thanks, this is okay for master, but could you perhaps add a sentence,
in the manual and in NEWS, about the exceptional situations when this
variable should be reset to nil? I think we should say something,
otherwise the need for the variable is questionable.