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: testing for a remote file to include file on a Windows mapped drive Date: Mon, 21 Apr 2008 12:17:01 -0400 Message-ID: References: <87bq781bf7.fsf@gmx.de> <000a01c8a314$5fff7630$0200a8c0@us.oracle.com> <000d01c8a324$97820590$0200a8c0@us.oracle.com> <000f01c8a334$b2a40660$0200a8c0@us.oracle.com> <000101c8a37f$eeb543d0$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1208794854 3054 80.91.229.12 (21 Apr 2008 16:20:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Apr 2008 16:20:54 +0000 (UTC) Cc: 'Emacs-Devel' , Drew Adams , 'Jason Rumney' To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 21 18:21:26 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JnylI-0000Fz-Sa for ged-emacs-devel@m.gmane.org; Mon, 21 Apr 2008 18:21:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jnyjf-0007x5-FN for ged-emacs-devel@m.gmane.org; Mon, 21 Apr 2008 12:19:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jnyja-0007wo-Tq for emacs-devel@gnu.org; Mon, 21 Apr 2008 12:19:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JnyjW-0007w7-8P for emacs-devel@gnu.org; Mon, 21 Apr 2008 12:19:14 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JnyjV-0007w4-WB for emacs-devel@gnu.org; Mon, 21 Apr 2008 12:19:10 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JnyiV-00007z-LB; Mon, 21 Apr 2008 12:19:00 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsAFABdbDEhMCpdU/2dsb2JhbACBUakb X-IronPort-AV: E=Sophos;i="4.25,690,1199682000"; d="scan'208";a="18825059" Original-Received: from smtp.pppoe.ca (HELO smtp.teksavvy.com) ([65.39.196.238]) by ironport2-out.teksavvy.com with ESMTP; 21 Apr 2008 12:17:01 -0400 Original-Received: from pastel.home ([76.10.151.84]) by smtp.teksavvy.com (Internet Mail Server v1.0) with ESMTP id BUM74801; Mon, 21 Apr 2008 12:17:01 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 708E18066; Mon, 21 Apr 2008 12:17:01 -0400 (EDT) In-Reply-To: (Michael Albinus's message of "Mon, 21 Apr 2008 17:13:32 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:95643 Archived-At: > I just see this function from a practical point of view, providing an > implementation for a special case (Tramp syntax). file-remote-p > is based on file name handler functions, that means it works over the > file name syntax. `file-remote-p' is not "based on file-name-handler function". Just like `copy-file', it is a file operation which can be overridden by file-name handlers. But for files accessed directly via the OS, it can (and should) provide any implementation it wants, according to its intended behavior. I know it started as a file-name-handler-only thingy, but its new docstring and this discussion shows that it goes further than that. > That's why I am not creative enough to see how to implement your > interpretation of that function. Maybe you're thinking of "how can I implement it in Tramp" whereas the Tramp-side of that function is already implemented and this thread is not only concerned about its behavior for non-file-name-handled files. Stefan