From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
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 13:04:25 +0200 [thread overview]
Message-ID: <83d2wtle12.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0gF+G3MnHpMbR-CvesdPbbqMe5f8kyEBRL7SG6PSZps=Q@mail.gmail.com>
> Date: Fri, 25 Jan 2013 10:34:45 +0100
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: michael.albinus@gmx.de, 13540@debbugs.gnu.org
>
> > > gdb emacs.exe
> > (gdb) break w32notify.c:206
> > (gdb) r
> >
> > should set you up. If the breakpoint breaks, GDB will complain that
> > sources are not available, so it cannot display the source. But it
> > doesn't matter, since all I'm interested in is whether it breaks and
> > if so, what do we get in io_info->hEvent object.
>
> 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.
> If the file is stored locally, it breaks two times when the file being
> watched is updated (I have to type `c' two times).
How did you "update the file", exactly? I just type something like
echo "foo" >> FILE
This results in only one notification, not two. Maybe your update
method causes the file to be modified twice in a row.
next prev parent reply other threads:[~2013-01-25 11:04 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 [this message]
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=83d2wtle12.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13540@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--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).