unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael.albinus@gmx.de, 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 08:46:59 +0100	[thread overview]
Message-ID: <CAH8Pv0hN_P9enqcBBz4xE=m5F54OFiH5YZ5p8Ete6hcxDNHU7g@mail.gmail.com> (raw)
In-Reply-To: <83r4lala3q.fsf@gnu.org>

> Each time you evaluate the expression that calls w32notify-add-watch,
> you should see another "New Thread" announcement.

Yes I do.

> This is normal,
> since each watch you add starts a new thread where the watching code
> runs.

Ok.

> Can you use Process Explorer or "pslist -d emacs" (both tools are from
> the Sysinternals package) to see if the threads started when you
> invoke w32notify-add-watch keep running, or die/exit?

I observe (with process explorer) that the new threads keep running.

> The lack of any messages suggests that the threads continue to run,
> but file notifications never come in, which probably means we cannot
> detect this problem automatically, and must rely on the users who know
> which volumes can and cannot be supported.

Ok, if Emacs cannot determine itself whether file notifications work,
I'll set `auto-revert-use-notify' to nil on that machine.

> Also, I presume that you tried to modify files on the mounted volumes,
> while you had GDB attached to Emacs.

Of course.  I started and "emacs -Q" process under GDB, and from that
emacs session I visited the file on the mounted volume and turned on
auto-revert-mode.  Then, if I modify the file with another program,
the emacs buffer isn't reverted and the GDB console doesn't show any
message.

-- 
Dani Moncayo





  reply	other threads:[~2013-01-25  7:46 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 [this message]
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='CAH8Pv0hN_P9enqcBBz4xE=m5F54OFiH5YZ5p8Ete6hcxDNHU7g@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=13540@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).