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 09:13:55 +0100 [thread overview]
Message-ID: <87pq0t65oc.fsf@gmx.de> (raw)
In-Reply-To: <83ip6llmoy.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Jan 2013 09:57:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I guess autorevert should allow users to specify whether notifications
> should be used on a per filesystem basis, rather than just globally
> for the entire session.
Makes sense to me. With this mechanism, a user could also decide,
whether remote files shall be reverted based on file notifications, or
not. I'll prepare a patch for autorevert.el.
Maybe we could also enhance the docstring of w32notify-add-watch, that
even a returned descriptor does not guarantee that the files are
watched. Whether we need it for inotify-add-watch as well I don't
know. I've tested shortly on an NFS mounted filesystem, which is
exported from my NAS, and there were no problems (notifications did
arrive). But the more interesting test might be SMB mounts, which I
haven't available locally. I should ask my wife to share something to me
from her laptop :-)
Best regards, Michael.
next prev parent reply other threads:[~2013-01-25 8:13 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 [this message]
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
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
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=87pq0t65oc.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 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).