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: [PATCH updated] Support for filesystem watching (inotify) Date: Tue, 07 Jun 2011 11:42:40 -0300 Message-ID: References: <201106040034.15598.ruediger@c-plusplus.de> <8762olmk6y.fsf@ambire.localdomain> <201106061825.25078.ruediger@c-plusplus.de> <871uz6hg1d.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1307460827 30058 80.91.229.12 (7 Jun 2011 15:33:47 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 7 Jun 2011 15:33:47 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 07 17:33:41 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QTyHl-0001sO-4m for ged-emacs-devel@m.gmane.org; Tue, 07 Jun 2011 17:33:41 +0200 Original-Received: from localhost ([::1]:35642 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTyHj-0001Mc-Pq for ged-emacs-devel@m.gmane.org; Tue, 07 Jun 2011 11:33:39 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:55199) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTxUT-00054v-Qu for emacs-devel@gnu.org; Tue, 07 Jun 2011 10:42:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QTxUS-00041f-7f for emacs-devel@gnu.org; Tue, 07 Jun 2011 10:42:45 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:52304) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTxUR-00041Z-Uy for emacs-devel@gnu.org; Tue, 07 Jun 2011 10:42:44 -0400 Original-Received: from 121-249-126-200.fibertel.com.ar ([200.126.249.121]:59884 helo=ceviche.home) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1QTxUR-0001Yd-82; Tue, 07 Jun 2011 10:42:43 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 9AC5B660DD; Tue, 7 Jun 2011 11:42:40 -0300 (ART) In-Reply-To: <871uz6hg1d.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 06 Jun 2011 15:16:14 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.10 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:140264 Archived-At: >>> The problem is: How to implement the file-unwatch then? I need a way >>> to identify each separate file-watch request. What would be the best >>> way to do that? SM> How about letting file-watch return a "file-watcher" which you then need SM> to pass to file-unwatch? This "file-watcher" could be any kind of Elisp SM> data you find convenient for this. You may decide to provide no other SM> operation than file-unwatch, but you could also decide to provided SM> additional operations such as changing the callback (I'm not saying SM> that would necessarily be a good idea, tho, but maybe other operations SM> would be handy). > (background: url-future.el is really a generic futures library, but the > only expected use for it currently is in url-*.el) > The "file-watcher" could derive from url-future, with the nice > error-catching and accessor functions that come with it, plus it's > protected from double-invocation. That doesn't sound right to me. At least I'm having trouble figuring out how to bend my mind such that this file-watcher matches (even coarsely) the concept of a "future". Stefan