From: Paul Eggert <eggert@cs.ucla.edu>
To: Bertrand Brelier <bertrand.brelier@gmail.com>
Cc: 19607@debbugs.gnu.org
Subject: bug#19607: issue with Emacs 24.4.1 but not with 24.3.1 : changed on disk; really edit the buffer
Date: Tue, 20 Jan 2015 01:39:26 -0800 [thread overview]
Message-ID: <54BE224E.80406@cs.ucla.edu> (raw)
In-Reply-To: <CADF9JrhYaY8HxtDMJw6qYjt-C1hg99fG_bx8rDh4gVnNpkbfWA@mail.gmail.com>
If memory serves, Emacs 24.4 is a bit more careful to detect race conditions
when a file changes while you're editing it, and most likely this is running
afoul of some aspect of encfs. I suggest running 'strace -o emacs.tr emacs -Q',
reproducing the problem, and looking at the resulting trace file. You can do
the same thing with both old and new Emacs and see how the traces differ. You
can email the traces to 19607@debbugs.gnu.org. We don't need the full traces,
just the parts relevant to accessing the files in question, notably the file
status and time stamps.
next prev parent reply other threads:[~2015-01-20 9:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 13:23 bug#19607: issue with Emacs 24.4.1 but not with 24.3.1 : changed on disk; really edit the buffer Bertrand Brelier
2015-01-20 9:39 ` Paul Eggert [this message]
2015-01-20 13:19 ` Bertrand Brelier
2015-01-21 0:21 ` Paul Eggert
2015-01-21 13:12 ` Bertrand Brelier
2015-01-22 2:20 ` Paul Eggert
2015-01-22 14:16 ` Bertrand Brelier
2015-01-22 20:55 ` Paul Eggert
2015-01-22 21:26 ` Bertrand Brelier
2015-01-22 22:42 ` Paul Eggert
2015-01-23 13:15 ` Bertrand Brelier
2015-01-23 22:27 ` Paul Eggert
2015-01-26 13:08 ` Bertrand Brelier
2015-01-26 19:43 ` Paul Eggert
2015-01-27 22:29 ` Paul Eggert
2015-01-27 23:04 ` Jakob Unterwurzacher
2015-01-28 4:56 ` Paul Eggert
2015-03-23 18:58 ` Glenn Morris
2015-03-24 0:13 ` Paul Eggert
2015-01-28 13:11 ` Bertrand Brelier
2015-01-26 23:08 ` Jakob Unterwurzacher
2015-01-27 21:30 ` bug#19607: issue with Emacs 24.4.1 but not with 24.3.1 : changed on disk; Jakob Unterwurzacher
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=54BE224E.80406@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=19607@debbugs.gnu.org \
--cc=bertrand.brelier@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 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).