From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <raaahh@gmail.com>
Cc: 13149@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#13149: 24.3.50; Emacs thinks file was changed outside Emacs, but it was not
Date: Fri, 18 Jan 2013 09:49:31 +0200 [thread overview]
Message-ID: <83d2x36id0.fsf@gnu.org> (raw)
In-Reply-To: <50F8CC6F.7000106@gmail.com>
> Date: Fri, 18 Jan 2013 08:15:43 +0400
> From: Dmitry Gutov <raaahh@gmail.com>
> CC: eggert@cs.ucla.edu, 13149@debbugs.gnu.org
>
> > I suspect that what you see is some bad interaction between VirtualBox
> > and the nasty way Windows disk cache optimizes its disk I/O. It is
> > known to update the file attributes lazily, so data could be written
> > to a file without the file's directory entry updated at the same time,
> > until some time later.
>
> I wonder why I don't see that with the straight Windows build editing
> files on the local filesystem.
This is speculation, but I presume that locally the file-I/O API calls
interact with the cached files better than what VirtualBox's Posix
emulation does.
Or maybe I'm wrong, and we will start seeing similar problems on
Windows, now that Emacs uses 'fstat' much more than it did a year or
so ago (when 'fstat' was not used in the native Windows build at all).
next prev parent reply other threads:[~2013-01-18 7:49 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 21:51 bug#13149: 24.3.50; Emacs thinks file was changed outside Emacs, but it was not Drew Adams
2012-12-11 22:48 ` Dmitry Gutov
2012-12-11 22:54 ` Drew Adams
2013-01-14 5:10 ` Dmitry Gutov
2013-01-14 14:57 ` Dmitry Gutov
2013-01-14 17:02 ` Eli Zaretskii
2013-01-14 22:22 ` Dmitry Gutov
2013-01-14 18:28 ` Paul Eggert
2013-01-14 22:20 ` Dmitry Gutov
2013-01-15 6:45 ` Paul Eggert
2013-01-15 8:54 ` Dmitry Gutov
2013-01-15 17:31 ` Paul Eggert
2013-01-15 21:38 ` Dmitry Gutov
2013-01-15 21:47 ` Paul Eggert
2013-01-15 22:11 ` Dmitry Gutov
2013-01-15 22:38 ` Paul Eggert
2013-01-15 23:09 ` Dmitry Gutov
2013-01-15 23:44 ` Dmitry Gutov
2013-01-16 5:57 ` Paul Eggert
2013-01-17 10:32 ` Dmitry Gutov
2013-01-17 17:05 ` Eli Zaretskii
2013-01-18 4:15 ` Dmitry Gutov
2013-01-18 7:49 ` Eli Zaretskii [this message]
2013-01-17 21:14 ` Paul Eggert
2013-01-18 4:55 ` Dmitry Gutov
2013-01-18 5:26 ` Paul Eggert
2013-01-17 21:33 ` Paul Eggert
2013-01-18 4:36 ` Dmitry Gutov
2013-01-18 5:01 ` Paul Eggert
2013-01-18 5:10 ` Dmitry Gutov
2013-01-18 5:25 ` Paul Eggert
2013-01-18 5:54 ` Dmitry Gutov
2013-01-18 6:22 ` Dmitry Gutov
2013-01-18 7:56 ` Eli Zaretskii
2013-01-18 14:45 ` Dmitry Gutov
2013-01-18 21:35 ` Paul Eggert
2013-01-18 22:52 ` Dmitry Gutov
2013-01-19 0:55 ` Paul Eggert
2013-01-19 1:09 ` Dmitry Gutov
2013-01-19 2:37 ` Paul Eggert
2013-01-19 4:02 ` Dmitry Gutov
2013-01-19 4:51 ` Paul Eggert
[not found] ` <DEB91990BBBB4255BFB466956EB54214@us.oracl! e.com>
[not found] ` <DEB91990BBBB4255BFB466956EB54214@us.oracl!>
[not found] ` <e.com@[87.69.4.28]>
[not found] ` <83wq! urc1u3.fsf@gnu.org>
[not found] ` <DEB91990BBBB4255BFB466956! EB54214@us.oracl!>
[not found] ` <DEB91990BBBB4255BFB466956EB54214@us.oracl!e.com>
2013-01-19 5:02 ` Drew Adams
2013-02-01 16:32 ` Drew Adams
2013-02-01 16:43 ` Drew Adams
2013-02-01 16:49 ` Drew Adams
2013-02-01 18:43 ` Eli Zaretskii
2013-02-01 19:19 ` Drew Adams
2013-02-01 19:36 ` Eli Zaretskii
2013-02-01 22:15 ` Drew Adams
2013-02-02 9:41 ` Eli Zaretskii
2013-02-02 16:06 ` Drew Adams
2013-02-01 19:38 ` Eli Zaretskii
2013-02-01 22:13 ` Drew Adams
2013-02-01 21:05 ` Paul Eggert
2013-02-01 22:14 ` Drew Adams
2013-02-01 22:22 ` Paul Eggert
2013-02-02 9:43 ` Eli Zaretskii
2013-03-19 8:39 ` Uwe Siart
2013-03-19 16:55 ` Eli Zaretskii
2013-03-19 17:50 ` Uwe Siart
2014-02-06 1:40 ` Lars Ingebrigtsen
2014-02-06 6:12 ` Drew Adams
2014-02-06 6:19 ` Eli Zaretskii
2013-02-02 9:38 ` Eli Zaretskii
2013-02-02 19:31 ` Paul Eggert
2013-01-18 7:57 ` Eli Zaretskii
2013-01-17 17:16 ` David Engster
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=83d2x36id0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13149@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=raaahh@gmail.com \
/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.