unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 60474@debbugs.gnu.org, orgmode@tec.tecosaur.net, yantar92@posteo.net
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	[thread overview]
Message-ID: <834jt92kzf.fsf@gnu.org> (raw)
In-Reply-To: <577bbae8-721e-8780-3b8d-f1cd531e3c13@cs.ucla.edu> (message from Paul Eggert on Sun, 1 Jan 2023 19:21:20 -0800)

> 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.





  parent reply	other threads:[~2023-01-02 12:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01 18:51 bug#60474: 30.0.50; `write-region-inhibit-fsync' and copy-on-write file systems Ihor Radchenko
2023-01-01 20:07 ` Eli Zaretskii
2023-01-02  3:21   ` Paul Eggert
2023-01-02  5:54     ` Ihor Radchenko
2023-01-02 12:23       ` Eli Zaretskii
2023-01-02 12:12     ` Eli Zaretskii [this message]
2023-01-02 19:38       ` Paul Eggert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=834jt92kzf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60474@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=orgmode@tec.tecosaur.net \
    --cc=yantar92@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).