From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Albinus Newsgroups: gmane.emacs.devel Subject: Re: filenotify.el Date: Wed, 26 Jun 2013 08:21:05 +0200 Message-ID: <87a9md2y0e.fsf@gmx.de> References: <87d2ra9z4x.fsf@gmx.de> <1383316.4Bc292dOgY@descartes> <87vc52yq04.fsf@gmx.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1372227683 29335 80.91.229.3 (26 Jun 2013 06:21:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 26 Jun 2013 06:21:23 +0000 (UTC) Cc: =?utf-8?Q?R=C3=BCdiger?= Sonderfeld , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 26 08:21:23 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 1Urj6V-0008OT-6h for ged-emacs-devel@m.gmane.org; Wed, 26 Jun 2013 08:21:19 +0200 Original-Received: from localhost ([::1]:43626 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Urj6U-0004DV-Eo for ged-emacs-devel@m.gmane.org; Wed, 26 Jun 2013 02:21:18 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59831) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Urj6Q-0004DB-SV for emacs-devel@gnu.org; Wed, 26 Jun 2013 02:21:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Urj6N-0003EE-OY for emacs-devel@gnu.org; Wed, 26 Jun 2013 02:21:14 -0400 Original-Received: from mout.gmx.net ([212.227.17.20]:55482) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Urj6N-0003Dv-FI for emacs-devel@gnu.org; Wed, 26 Jun 2013 02:21:11 -0400 Original-Received: from mailout-de.gmx.net ([10.1.76.12]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0LbfGf-1UOkHe1wiZ-00lGIe for ; Wed, 26 Jun 2013 08:21:09 +0200 Original-Received: (qmail invoked by alias); 26 Jun 2013 06:21:09 -0000 Original-Received: from p5B2980C1.dip0.t-ipconnect.de (EHLO detlef.gmx.de) [91.41.128.193] by mail.gmx.net (mp012) with SMTP; 26 Jun 2013 08:21:09 +0200 X-Authenticated: #3708877 X-Provags-ID: V01U2FsdGVkX1/V7EZ4+PfVSNdbVN4S+DGiQE8ZvAH1/483jOJ++O UKHYL66eQtjTPd In-Reply-To: (Stefan Monnier's message of "Tue, 25 Jun 2013 20:11:46 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 212.227.17.20 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:161072 Archived-At: Stefan Monnier writes: >> Just to be sure. The different low-level packages are not fully >> compatible (event names differ, for example); it would be a nightmare >> for filenotify.el when the different packages compete under the hood. > > Why would they compete? In the unlikely case that both gfilenotify and > inotify are provided, can't the code just use one of the two without > being impacted by the other? If not, why not? Can we fix it so as to > avoid such conflicts? [...] > Agreed, but the better option is to make sure they don't conflict with > each other, and then make filenotify.el choose one of the available ones > "arbitrarily". Well, filenotify.el shall decide for one of the available low-level packages, and use it. I'll change accordingly. However, any Lisp package could still decide to activate "the other" low-level file notification package if linked to Emacs. In this case, we must ensure that the incoming file-notify events can be distinguished. Such an event looks like (DESCRIPTOR ACTION FILE). Different low-level packages must use unique DESCRIPTORs then. As of today, this is not guaranteed; both gfilenotify and inotify use integers for example. There's no urgency for this; as of today Emacs' configure decides for one and only one package. And in Tramp I use already descriptors which are unique for Tramp (it's the internal Tramp vector for the file to be monitored). > Stefan Best regards, Michael.