From xemacs-m  Tue Feb 25 05:25:26 1997
Received: from palrel3.hp.com (palrel3.hp.com [15.253.88.10])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id FAA02365
	for <xemacs-beta@xemacs.org>; Tue, 25 Feb 1997 05:25:25 -0600 (CST)
Received: from cuckoo.hpl.hp.com (cuckoo.hpl.hp.com [15.144.62.116]) by palrel3.hp.com with ESMTP (8.7.5/8.7.3) id DAA04241; Tue, 25 Feb 1997 03:25:11 -0800 (PST)
Received: (from ange@localhost) by cuckoo.hpl.hp.com (8.7.1/8.7.1) id LAA01854; Tue, 25 Feb 1997 11:25:10 GMT
Sender: ange@cuckoo.hpl.hp.com
To: kifer@CS.SunySB.EDU (Michael Kifer)
Cc: Jonathan Edwards <edwards@intranet.com>, xemacs-beta@xemacs.org
Subject: Re: ediff problem  and EFS
References: <199702250205.VAA29652@cs.sunysb.edu>
From: Andy Norman <ange@hplb.hpl.hp.com>
Date: 25 Feb 1997 11:25:09 +0000
In-Reply-To: kifer@CS.SunySB.EDU's message of Mon, 24 Feb 1997 20:53:58 -0500
Message-ID: <x5hgj13z6y.fsf@cuckoo.hpl.hp.com>
Lines: 23
X-Mailer: Gnus v5.2.37/XEmacs 19.14

kifer@CS.SunySB.EDU (Michael Kifer) writes:

> Well, it needs to know if you are working with remote files or not.
> XEmacs now has file-remote-p, but this function loads efs.
> The right thing is to write remote.el, which should be much smaller than
> EFS. It should yank the implementation of efs-ftp-path from efs, and should
> be able to recognize URLs as well.  

> Whoever has the time to write this stuff gets an internet kudo...

;-)

> If efs-ftp-path were isolated into efs-remote.el or something like
> that, I could then load just this file.

If you have efs-auto loaded, you can use efs-ftp-path.  This will only load
efs if the remote path requires loading the whole of efs to perform some
operation.  Alternatively, there is a module called efs-cu which may make your
life easier.
-- 
						-- ange -- <><

http://www-uk.hpl.hp.com/people/ange		ange@hplb.hpl.hp.com

