From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13540@debbugs.gnu.org
Subject: bug#13540: 24.3.50; Regression in trunk: auto-revert-mode fails on files accessed via samba
Date: Fri, 25 Jan 2013 14:29:35 +0100 [thread overview]
Message-ID: <87fw1p5r28.fsf@gmx.de> (raw)
In-Reply-To: <83d2wtle12.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Jan 2013 13:04:25 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> If the file is in the network volume, it doesn't break.
>
> Thanks. So I guess user customizations is the only way to deal with
> this.
Well, I have committed this to trunk in revision #111603. There is now
an option `auto-revert-notify-exclude-dir-regexp', which could be used
to exclude directories from file notifications, and let files
autorevert via the file checks as done until now. Dani, in your case it
might be sufficient to apply
(setq auto-revert-notify-exclude-dir-regexp (regexp-quote "t:\myfile"))
I gave that option an initial value to exclude mounted files and remote
files. This value might be tuned in further tests.
With this patch I have also committed two other changes which I have
tested last days:
- File notifications are established for directories instead of single
files. w32notify does it by default already, and for the inotify setup
this is achieved by watching default-directory in autorevert.
- There is a new option `auto-revert-remote-files', which allows you to
revert remote files. Until now, remote files were excluded. The
default value of this option is nil.
I've started also performance tests, in order to see the difference
between file notifications and explicit file checks. This is not
finished yet.
Best regards, Michael.
next prev parent reply other threads:[~2013-01-25 13:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 8:55 bug#13540: 24.3.50; Regression in trunk: auto-revert-mode fails on files accessed via samba Dani Moncayo
2013-01-24 10:13 ` Michael Albinus
2013-01-24 10:20 ` Dani Moncayo
2013-01-24 10:23 ` Michael Albinus
2013-01-24 16:22 ` Eli Zaretskii
2013-01-24 16:34 ` Dani Moncayo
2013-01-24 16:37 ` Dani Moncayo
2013-01-24 16:53 ` Eli Zaretskii
2013-01-24 17:23 ` Dani Moncayo
2013-01-24 17:28 ` Dani Moncayo
2013-01-24 17:39 ` Eli Zaretskii
2013-01-24 17:43 ` Eli Zaretskii
2013-01-24 17:44 ` Dani Moncayo
2013-01-24 18:13 ` Dani Moncayo
2013-01-24 18:29 ` Eli Zaretskii
2013-01-24 18:16 ` Eli Zaretskii
2013-01-25 7:46 ` Dani Moncayo
2013-01-25 7:57 ` Eli Zaretskii
2013-01-25 8:13 ` Michael Albinus
2013-01-25 9:41 ` Eli Zaretskii
2013-01-25 8:18 ` Eli Zaretskii
2013-01-25 8:29 ` Dani Moncayo
2013-01-25 9:27 ` Eli Zaretskii
2013-01-25 9:34 ` Dani Moncayo
2013-01-25 11:04 ` Eli Zaretskii
2013-01-25 11:19 ` Dani Moncayo
2013-01-25 13:44 ` Eli Zaretskii
2013-01-25 13:29 ` Michael Albinus [this message]
2013-02-14 10:09 ` Michael Albinus
2013-01-24 16:32 ` Eli Zaretskii
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=87fw1p5r28.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=13540@debbugs.gnu.org \
--cc=eliz@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.