From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: testing for a remote file to include file on a Windows mapped drive Date: Sat, 26 Jan 2008 08:55:48 -0800 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1201366689 24057 80.91.229.12 (26 Jan 2008 16:58:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 26 Jan 2008 16:58:09 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Eli Zaretskii" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 26 17:58:28 2008 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 1JIoMK-0001IQ-8n for ged-emacs-devel@m.gmane.org; Sat, 26 Jan 2008 17:58:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JIoLt-0000HE-Tr for ged-emacs-devel@m.gmane.org; Sat, 26 Jan 2008 11:57:57 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JIoLE-0008Nb-QJ for emacs-devel@gnu.org; Sat, 26 Jan 2008 11:57:16 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JIoLE-0008NI-6f for emacs-devel@gnu.org; Sat, 26 Jan 2008 11:57:16 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JIoLD-0008N9-RE for emacs-devel@gnu.org; Sat, 26 Jan 2008 11:57:15 -0500 Original-Received: from agminet01.oracle.com ([141.146.126.228]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JIoL9-0006AR-2F; Sat, 26 Jan 2008 11:57:11 -0500 Original-Received: from rgmgw2.us.oracle.com (rgmgw2.us.oracle.com [138.1.186.111]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id m0QGv1Gj016187; Sat, 26 Jan 2008 10:57:01 -0600 Original-Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by rgmgw2.us.oracle.com (Switch-3.2.4/Switch-3.2.4) with ESMTP id m0QGINWN011881; Sat, 26 Jan 2008 09:57:00 -0700 Original-Received: from inet-141-146-46-1.oracle.com by acsmt350.oracle.com with ESMTP id 3538126391201366546; Sat, 26 Jan 2008 08:55:46 -0800 Original-Received: from dradamslap1 (/141.144.72.89) by bhmail.oracle.com (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 26 Jan 2008 08:55:46 -0800 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 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:87585 Archived-At: > > . file-remote-p > > . ffap-file-remote-p > > . dired-sort-menu-remote-p > > "\\`/\\([^@:/]+@\\)?\\([^:/]+\\):" > > . ange-ftp-name-format > > "\\`/\\(\\([^/:]*\\)@\\)?\\([^@/:]*[^@/:.]\\):\\(.*\\)" > > . remote (ange-ftp) filenames (see make-auto-save-file-name) > > "^/\\w+@[-A-Za-z0-9._]+:" > > . ffap-ftp-regexp > > "\\`/[^/:]+:" > > These all make sense only in the context of the features that define > them. In general, Emacs does not consider files on a mounted volume > to be remote. The notion of remote files is in conjunction with Emacs > features that access files in ways that are not the normal filesystem > APIs. > > It sounds like you want something entirely different As I said, I want to know if a file name is likely to represent a remote file (in the Emacs sense you cited) or a file on a mapped network drive. The reason is to avoid the time needed to access the remote machine. That's the same reason that most of the above were defined, but they don't handle the network-drive case.