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: filenotify.el Date: Tue, 25 Jun 2013 20:11:46 -0400 Message-ID: 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 1372205517 30204 80.91.229.3 (26 Jun 2013 00:11:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 26 Jun 2013 00:11:57 +0000 (UTC) Cc: =?iso-8859-1?Q?R=FCdiger?= Sonderfeld , emacs-devel@gnu.org To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 26 02:11:54 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 1UrdKz-0008QH-5B for ged-emacs-devel@m.gmane.org; Wed, 26 Jun 2013 02:11:53 +0200 Original-Received: from localhost ([::1]:33550 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UrdKy-00071i-Mf for ged-emacs-devel@m.gmane.org; Tue, 25 Jun 2013 20:11:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40809) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UrdKv-00070R-21 for emacs-devel@gnu.org; Tue, 25 Jun 2013 20:11:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UrdKu-0002WG-3l for emacs-devel@gnu.org; Tue, 25 Jun 2013 20:11:48 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:59874) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UrdKt-0002W8-W5 for emacs-devel@gnu.org; Tue, 25 Jun 2013 20:11:48 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFMCppA/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GsR+QDpEKA6R6gV6DEw X-IPAS-Result: Av4EABK/CFFMCppA/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GsR+QDpEKA6R6gV6DEw X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="17168424" Original-Received: from 76-10-154-64.dsl.teksavvy.com (HELO pastel.home) ([76.10.154.64]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 25 Jun 2013 20:11:41 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id B89C6678F1; Tue, 25 Jun 2013 20:11:46 -0400 (EDT) In-Reply-To: <87vc52yq04.fsf@gmx.de> (Michael Albinus's message of "Tue, 25 Jun 2013 21:00:43 +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:161064 Archived-At: > 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? > In general, it could be possible to apply several low-level file > notification libraries in parallel. But this wouldn't bring additional > features, so we should avoid this. 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". We may also want to tweak configure to avod building Emacs with support for multiple file notification systems, but if we assume a future with FFI, then multiple notification systems may occur dynamically and there isn't any good reason to really disallow it. Stefan