unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 13540@debbugs.gnu.org
Subject: bug#13540: 24.3.50; Regression in trunk: auto-revert-mode fails on files accessed via samba
Date: Thu, 24 Jan 2013 11:13:52 +0100	[thread overview]
Message-ID: <8738xq3n33.fsf@gmx.de> (raw)
In-Reply-To: <CAH8Pv0gfFgV5bG2YxsZ0L939QkW1L2VOB2QLyo8sgpAc_vJZWQ@mail.gmail.com> (Dani Moncayo's message of "Thu, 24 Jan 2013 09:55:13 +0100")

Dani Moncayo <dmoncayo@gmail.com> writes:

> Hello,

Hi Dani,

> At work, I've just observed a regression in the trunk [1] wrt the
> emacs-24 branch [2].
>
> If I visit some file, say "t:\myfile" (where t: is a network unit,
> mounted via samba, that points to an hp-ux server), and I enable
> auto-revert-mode, the buffer is not reverted when some other program
> changes the contents of the file.
>
> The problem doesn't show up when the file is stored in a local unit
> (c:\) but fails in the above case.

There are recent changes in autorevert.el. If possible, file
notifications will be used, in order to be triggered by the file system
if a file is modified. For Windows systems, the new function
`w32notify-add-watch' is used.

Likely, it is not possible to enable file notifications for mounted file
systems under Windows. In that case, `w32notify-add-watch' shall return
nil, and the code in auto-revert.el shall fall back to the previous
implementation.

Could you, please, check what

(w32notify-add-watch "t:\myfile" '(size last-write-time) 'ignore)

returns?

Best regards, Michael.





  reply	other threads:[~2013-01-24 10: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 [this message]
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
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=8738xq3n33.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=13540@debbugs.gnu.org \
    --cc=dmoncayo@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).