From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.bugs Subject: bug#22454: 24.5; win32 file-notify, input events caused by updates to other (non-watched) files Date: Sun, 24 Jan 2016 11:46:14 -0500 Message-ID: References: <83a8nv3sy3.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1453654037 2806 80.91.229.3 (24 Jan 2016 16:47:17 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 24 Jan 2016 16:47:17 +0000 (UTC) Cc: 22454-done@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Jan 24 17:47:10 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aNNok-0001cS-EB for geb-bug-gnu-emacs@m.gmane.org; Sun, 24 Jan 2016 17:47:10 +0100 Original-Received: from localhost ([::1]:60998 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNNoj-00075w-NR for geb-bug-gnu-emacs@m.gmane.org; Sun, 24 Jan 2016 11:47:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40807) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNNof-00074W-KB for bug-gnu-emacs@gnu.org; Sun, 24 Jan 2016 11:47:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aNNoc-00044W-F4 for bug-gnu-emacs@gnu.org; Sun, 24 Jan 2016 11:47:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:46867) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNNoc-00044M-BE for bug-gnu-emacs@gnu.org; Sun, 24 Jan 2016 11:47:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aNNoc-0002Dz-5L for bug-gnu-emacs@gnu.org; Sun, 24 Jan 2016 11:47:02 -0500 Resent-From: Noam Postavsky Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Sun, 24 Jan 2016 16:47:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 22454 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Mail-Followup-To: 22454@debbugs.gnu.org, npostavs@users.sourceforge.net, npostavs@users.sourceforge.net Original-Received: via spool by 22454-done@debbugs.gnu.org id=D22454.14536539817845 (code D ref 22454); Sun, 24 Jan 2016 16:47:01 +0000 Original-Received: (at 22454-done) by debbugs.gnu.org; 24 Jan 2016 16:46:21 +0000 Original-Received: from localhost ([127.0.0.1]:35085 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aNNnx-00022I-Ar for submit@debbugs.gnu.org; Sun, 24 Jan 2016 11:46:21 -0500 Original-Received: from mail-io0-f177.google.com ([209.85.223.177]:36148) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aNNnw-0001va-18 for 22454-done@debbugs.gnu.org; Sun, 24 Jan 2016 11:46:20 -0500 Original-Received: by mail-io0-f177.google.com with SMTP id g73so133987326ioe.3 for <22454-done@debbugs.gnu.org>; Sun, 24 Jan 2016 08:46:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=nLYv1EFTXh/OPDJTKKfr4ai0IAwrPMizx4Pol9M5VOk=; b=Mo9lgAi675oaPdnFmzMpfZm0CjDAtgo0M/EZ8uWx+SrlXoOlBZxn672CEGmmauamL7 1Vg4xJ5d3KVt3I+nf23uPw7sOIEmBOjnFBY5r1L2/NntiAzWAmrmYrPvERR4i3mlIHkl oun9vwvD6uFHcwWL03CTPayPiOl8PHvN0h925lh/kXNipFO1ujdtCyA8R0w0GT+Rmu9s LnvX4Pw3CBfis7+vhoHXTKmsA4EaASV8Nl4C0v1L6QZ/5QcDCkePMlofjF4aFIY9I65T J1DOk9Rlg+6jGmsHhsnXltwDKaP870jG9XbuP8WGsbWOzCqtl9uDtpuaSVRyHqpwBp8K bA4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=nLYv1EFTXh/OPDJTKKfr4ai0IAwrPMizx4Pol9M5VOk=; b=l0Y2nvXp8aqUaZElsjAJ1AHPIM3gXt9B3rwK/YiqgyFW45b4fRKYC8c/vI0g+ktvMw /SEzIbK20WejuwAqy7vuwfcUbWp59NXqpMCuYwqJu5VqRWJAUMkh5nt5kz6iliyo1t3l f/qtQYwx6VkrTMEendvlRf3BrfxxFvyqmmYVTqzS4woBFG33QqK26WN5uU+VglQAMP6u p0uNRPJ1zs+UYL4vCUq6Id+dQxBI1RhMbob6Q9yo7kosq/2H0cXmlE5n2PTDMfLe2YOO RcbxDEeZmeId6gaSfcau7d7RWvP9LY8OriGqwZtoW8UffmOUzi1MARIfM9f/10+xlofb FNRw== X-Gm-Message-State: AG10YOQUnTEOUX8DxIgG9kMX9EehEVuiHiKgdQvvd4aYnm8es1gNXLPpmjE31n4VsO5FgLTgfG9+Dm0wjypfcQ== X-Received: by 10.107.10.65 with SMTP id u62mr12983688ioi.120.1453653974231; Sun, 24 Jan 2016 08:46:14 -0800 (PST) Original-Received: by 10.79.79.132 with HTTP; Sun, 24 Jan 2016 08:46:14 -0800 (PST) In-Reply-To: <83a8nv3sy3.fsf@gnu.org> X-Google-Sender-Auth: bzcj_S59bIw8Jabff5e4e21k2_A X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:111924 Archived-At: On Sun, Jan 24, 2016 at 10:20 AM, Eli Zaretskii wrote: > When you ask to watch a file, file-notify-add-watch actually watches > the entire directory of that file Oh. In this case I thought it was only files beneath .git/ that were being changed (while we we are watching a file in the working copy), but (trace-function 'file-notify-callback) tells me that Emacs is receiving events about the .git/ directory. >> This does not occur on GNU/Linux systems. > > Did those systems use inotify or the gfilenotify back-end? I think gfilenotify, but I only have access to a Windows box for the next couple of weeks, so I'm not 100% sure. > I don't think it's either a bug or a limitation. File notifications > generate input events, so the current implementation of sit-for has a > good reason to stop waiting. The way the input events are generated > differ between different back-ends, so perhaps the difference in > behavior you see is due to that, but in general I think the fact that > you didn't see that on GNU/Linux is more luck than anything else. Ok, sounds like there is nothing to fix on the Emacs side, so I'm closing this.