From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Added inotify support. Date: Sun, 07 Oct 2012 16:28:17 +0200 Message-ID: <87lifi1hmm.fsf@wanadoo.es> References: <2181827.T3JxG88qQt@descartes> <83lifoa7hr.fsf@gnu.org> <87obkkcu92.fsf@wanadoo.es> <87lifkvoxl.fsf@spindle.srvr.nix> <87ehlbtv0r.fsf@spindle.srvr.nix> <87626ntowb.fsf@spindle.srvr.nix> <87txu7s31q.fsf@spindle.srvr.nix> <87haq6ell2.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1349620116 5558 80.91.229.3 (7 Oct 2012 14:28:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 7 Oct 2012 14:28:36 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 07 16:28:43 2012 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 1TKrqU-00064y-Qn for ged-emacs-devel@m.gmane.org; Sun, 07 Oct 2012 16:28:42 +0200 Original-Received: from localhost ([::1]:51535 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TKrqO-0007sr-TY for ged-emacs-devel@m.gmane.org; Sun, 07 Oct 2012 10:28:36 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:57133) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TKrqN-0007si-1h for emacs-devel@gnu.org; Sun, 07 Oct 2012 10:28:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TKrqM-0005LT-37 for emacs-devel@gnu.org; Sun, 07 Oct 2012 10:28:34 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:32963) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TKrqL-0005KP-SF for emacs-devel@gnu.org; Sun, 07 Oct 2012 10:28:34 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TKrqP-00062S-Tl for emacs-devel@gnu.org; Sun, 07 Oct 2012 16:28:37 +0200 Original-Received: from 161.red-83-34-29.dynamicip.rima-tde.net ([83.34.29.161]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 Oct 2012 16:28:37 +0200 Original-Received: from ofv by 161.red-83-34-29.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 Oct 2012 16:28:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 22 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 161.red-83-34-29.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux) Cancel-Lock: sha1:zoM2NMI26BVY+VHv4Nx3Cnyp0Ng= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:154185 Archived-At: Stefan Monnier writes: >>> > I have no intention to rip out polling. Rather I hope that the >>> > higher-level API we come up with can be implemented by any of Windows's >>> > low-level API, inotify, MacOSX's equvalent, or polling. >>> ... which is what I hoped to hear. >> Plus combinations of the above, as needed. Right? > > If someone bothers to implement it, why not, tho I'm not sure how > important that would be (unless that patch can automatically figure out > when to use which). In theory, it is possible to automatically figure out when to use polling and when to use the OS notification features. But if inotify doesn't work on some filesystems, we need a method for detecting those filesystems. Does inotify report "I don't work on this" when it is used on those unsupported filesystems? Eli and I discussed the high level Lisp API for filesystem notifications. I think it is compatible with polling, in the sense that it can transparently fall back to polling, once the issue mentioned on the previous paragraph is addressed.