From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: File watch support in autorevert.el Date: Fri, 11 Jan 2013 10:57:00 -0500 Message-ID: References: <878v819kok.fsf@gmx.de> <83fw28uj9c.fsf@gnu.org> <8338y7vkyx.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1357919829 21613 80.91.229.3 (11 Jan 2013 15:57:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 11 Jan 2013 15:57:09 +0000 (UTC) Cc: michael.albinus@gmx.de, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 11 16:57:26 2013 Return-path: Envelope-to: ged-emacs-devel@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 1Ttgyz-0003KR-BD for ged-emacs-devel@m.gmane.org; Fri, 11 Jan 2013 16:57:25 +0100 Original-Received: from localhost ([::1]:40176 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ttgyj-0003rI-EQ for ged-emacs-devel@m.gmane.org; Fri, 11 Jan 2013 10:57:09 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:44061) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ttgyg-0003qz-M4 for emacs-devel@gnu.org; Fri, 11 Jan 2013 10:57:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ttgyf-0007bO-0F for emacs-devel@gnu.org; Fri, 11 Jan 2013 10:57:06 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:42754) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ttgyc-0007b6-6z; Fri, 11 Jan 2013 10:57:02 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtkGAG6Zu09MCpYP/2dsb2JhbABEgXuyFoEIghUBAQQBViMQCzQSFBgNJIgcBboJkEQDiEKacYFYgwc X-IronPort-AV: E=Sophos;i="4.75,637,1330923600"; d="scan'208";a="212302606" Original-Received: from 76-10-150-15.dsl.teksavvy.com (HELO pastel.home) ([76.10.150.15]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 11 Jan 2013 10:57:01 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 0AE2459441; Fri, 11 Jan 2013 10:57:00 -0500 (EST) In-Reply-To: <8338y7vkyx.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Jan 2013 16:43:34 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:156224 Archived-At: >> But at the same time, it's often preferable to wait a bit longer for the >> application to finish writing the new version of the file. I think the >> perfect behavior lies somewhere in-between: when we get an >> IN_CLOSE_WRITE, we should revert immediately, but when we get an >> IN_MODIFY we should revert "soon". > You mean, with a timer? Yes. Stefan