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: Mon, 06 Jun 2011 14:11:12 -0300 Message-ID: References: <201106040034.15598.ruediger@c-plusplus.de> <8762olmk6y.fsf@ambire.localdomain> <201106061825.25078.ruediger@c-plusplus.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1307390296 29484 80.91.229.12 (6 Jun 2011 19:58:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 6 Jun 2011 19:58:16 +0000 (UTC) Cc: Thien-Thi Nguyen , emacs-devel@gnu.org To: =?iso-8859-1?Q?R=FCdiger?= Sonderfeld Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 06 21:58:10 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 1QTfw9-000492-Nn for ged-emacs-devel@m.gmane.org; Mon, 06 Jun 2011 21:58:09 +0200 Original-Received: from localhost ([::1]:59276 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTfw8-0000qF-FY for ged-emacs-devel@m.gmane.org; Mon, 06 Jun 2011 15:58:08 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:48220) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTdKh-0007Ii-HA for emacs-devel@gnu.org; Mon, 06 Jun 2011 13:11:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QTdKg-0003gj-0E for emacs-devel@gnu.org; Mon, 06 Jun 2011 13:11:19 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:42693) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QTdKf-0003gf-Na for emacs-devel@gnu.org; Mon, 06 Jun 2011 13:11:17 -0400 Original-Received: from 213-159-126-200.fibertel.com.ar ([200.126.159.213]:44309 helo=ceviche.home) by fencepost.gnu.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1QTdKe-0002CB-99; Mon, 06 Jun 2011 13:11:16 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 78FAD660DD; Mon, 6 Jun 2011 14:11:12 -0300 (ART) In-Reply-To: <201106061825.25078.ruediger@c-plusplus.de> (=?iso-8859-1?Q?=22R=FCdiger?= Sonderfeld"'s message of "Mon, 6 Jun 2011 18:25:24 +0200") 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:140237 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? How about letting file-watch return a "file-watcher" which you then need to pass to file-unwatch? This "file-watcher" could be any kind of Elisp data you find convenient for this. You may decide to provide no other operation than file-unwatch, but you could also decide to provided additional operations such as changing the callback (I'm not saying that would necessarily be a good idea, tho, but maybe other operations would be handy). Stefan