From: Mark Karpov <markkarpov@openmailbox.org>
To: <20943@debbugs.gnu.org>
Subject: bug#20943: 25.0.50; Dired buffers are not always auto-reverterd
Date: Wed, 01 Jul 2015 13:23:01 +0600 [thread overview]
Message-ID: <87wpyk9wa2.fsf@openmailbox.org> (raw)
In-Reply-To: <87y4j1oy87.fsf@openmailbox.org>
OK, I've spent an hour testing it, trying to find some way to reliably
reproduce the problem. It's quite random, but I've found a way to
reproduce it in about 50% of cases.
> Does it happen with some specific type of directories, like those
> mounted in some special way?
No, I can reproduce this in my home directory, which is not mounted in
any unusual way.
> Furthermore, which kind of changes of the directory are you referring
> to? Reading `dired-buffer-stale-p', the dired buffer shall be reverted
> only if there is a new file in the directory, or a file is
> removed. Just changing (the timestamp of) a file in the directory
> shall not revert the dired buffer.
By changes I mean deletion of files or creation of files, see below.
How to reproduce:
1. emacs -Q
2. Open some directory in Dired.
3. Invoke shell or Emacs shell. Now I think this bug is most likely
happens when directory is changed in an automated way (maybe I'm
mistaken). Personally I use a script that transforms some files
(script written in Python, splits music files according to CUE file +
some magic, but it doesn't really matter). That means that some files
are created and old files are deleted.
4. Once I press C-m or Enter, there are two possible cases (each having
about 50 % probability): either all changes are reflected in Dired
buffer (that's in other window, window in Emacs sense of the word),
or all the changes go invisible and I have to switch to Dired buffer
and press g to see results.
That's pretty much all I can say. Not very helpful, but this is how I
can more or less reliably reproduce it.
> A second thought: auto-reverting dired buffers has been changed to use
> file notifications. Does it make a difference, when you eval the form
> (setq auto-revert-use-notify nil) ?
I'll test it as soon as I can.
next prev parent reply other threads:[~2015-07-01 7:23 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 18:19 bug#20943: 25.0.50; Dired buffers are not always auto-reverterd Mark Karpov
2015-06-30 19:58 ` Eli Zaretskii
2015-07-01 5:58 ` Michael Albinus
2015-07-01 7:15 ` Mark Karpov
2015-07-01 8:55 ` Michael Albinus
2015-07-01 9:09 ` Mark Karpov
2015-07-01 15:38 ` Eli Zaretskii
2015-07-01 15:25 ` Eli Zaretskii
[not found] ` <87y4j0fj8m.fsf@openmailbox.org>
2015-07-01 15:24 ` Eli Zaretskii
2015-07-02 8:02 ` Mark Karpov
2015-07-02 14:52 ` Eli Zaretskii
2015-07-03 7:33 ` Mark Karpov
2015-07-03 8:18 ` Eli Zaretskii
2015-07-03 9:39 ` Mark Karpov
2015-07-03 12:10 ` Eli Zaretskii
2015-07-03 12:37 ` Mark Karpov
2015-07-03 13:02 ` Mark Karpov
2015-07-03 13:43 ` Eli Zaretskii
2015-07-03 13:49 ` Mark Karpov
2015-07-03 16:08 ` Mark Karpov
2015-07-04 8:31 ` Eli Zaretskii
2015-07-04 8:49 ` Mark Karpov
2015-07-04 9:20 ` Michael Albinus
2015-07-04 9:32 ` Eli Zaretskii
2015-07-04 14:35 ` Drew Adams
2015-07-04 14:33 ` Drew Adams
2015-07-01 7:23 ` Mark Karpov [this message]
2015-07-02 10:49 ` Mark Karpov
2015-07-09 13:24 ` bug#20943: 25.0.50; Dired buffers are not always auto-reverted Mark Karpov
2015-07-09 14:47 ` Eli Zaretskii
2015-07-09 15:30 ` Mark Karpov
2015-07-09 18:41 ` Michael Albinus
2015-07-09 19:42 ` Mark Karpov
2015-07-10 5:46 ` Eli Zaretskii
2015-07-10 6:01 ` Michael Albinus
2015-07-10 7:10 ` Eli Zaretskii
2015-07-10 8:46 ` Michael Albinus
2015-07-16 18:12 ` Michael Albinus
2015-07-17 20:40 ` Mark Karpov
2015-07-18 10:37 ` Michael Albinus
2015-07-18 18:20 ` Mark Karpov
2015-07-14 16:28 ` Michael Albinus
2015-07-09 19:50 ` Mark Karpov
2015-07-10 5:43 ` Eli Zaretskii
2015-07-10 6:20 ` Mark Karpov
2015-07-10 7:13 ` Eli Zaretskii
2015-07-10 7:46 ` Mark Karpov
2015-07-10 8:03 ` Eli Zaretskii
2015-07-09 15:40 ` Mark Karpov
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=87wpyk9wa2.fsf@openmailbox.org \
--to=markkarpov@openmailbox.org \
--cc=20943@debbugs.gnu.org \
/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.