From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 60474@debbugs.gnu.org, orgmode@tec.tecosaur.net, eggert@cs.ucla.edu
Subject: bug#60474: 30.0.50; `write-region-inhibit-fsync' and copy-on-write file systems
Date: Mon, 02 Jan 2023 14:23:45 +0200 [thread overview]
Message-ID: <831qod2kha.fsf@gnu.org> (raw)
In-Reply-To: <87o7rh5vng.fsf@localhost> (message from Ihor Radchenko on Mon, 02 Jan 2023 05:54:11 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, 60474@debbugs.gnu.org,
> orgmode@tec.tecosaur.net
> Date: Mon, 02 Jan 2023 05:54:11 +0000
>
> Paul Eggert <eggert@cs.ucla.edu> writes:
>
> > On 2023-01-01 12:07, Eli Zaretskii wrote:
> >
> >> 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.
>
> What about Emacs DOS port and the likes? May be there some gotchas about
> specific file systems in non-standard OS?
Those systems have much more conservative filesystems, so they rarely
need fsync in the "usual" cases.
> Also, what would be the special situations you are talking about?
Right, that's my question as well. I presume when writing some
precious data, or maybe some transaction-like I/O.
next prev parent reply other threads:[~2023-01-02 12:23 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 [this message]
2023-01-02 12:12 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831qod2kha.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.