From xemacs-m  Mon Feb 24 19:56:38 1997
Received: from cs.sunysb.edu (sbcs.sunysb.edu [130.245.1.15])
	by xemacs.org (8.8.5/8.8.5) with SMTP id TAA20335
	for <xemacs-beta@xemacs.org>; Mon, 24 Feb 1997 19:56:35 -0600 (CST)
Received: from sbkifer.cs.sunysb.edu (sbkifer.cs.sunysb.edu [130.245.1.35]) by cs.sunysb.edu (8.6.12/8.6.9) with SMTP id VAA29652; Mon, 24 Feb 1997 21:05:38 -0500
Message-Id: <199702250205.VAA29652@cs.sunysb.edu>
X-Authentication-Warning: sbcs.cs.sunysb.edu: Host sbkifer.cs.sunysb.edu didn't use HELO protocol
From: kifer@CS.SunySB.EDU (Michael Kifer)
To: Jonathan Edwards <edwards@intranet.com>
cc: xemacs-beta@xemacs.org
Subject: Re: ediff problem  and EFS
In-reply-to: "Jonathan Edwards" of Mon, 24 Feb 1997 20:11:48 EST
             <199702250111.UAA15972@blight.IntraNet.com> 
Date: Mon, 24 Feb 1997 20:53:58 -0500
Sender: kifer@CS.SunySB.EDU



> In 20.1b2, ediff gets the error:
> symbol's function definition is void:efs-ftp-path
> 
> This seems related to the following new code in ediff-init.el:
> 
> (or (fboundp 'ediff-file-remote-p) ; user supplied his own function
>     (defun ediff-file-remote-p (file-name)
>       (car (cond ((featurep 'efs) (efs-ftp-path file-name))
> 		 ((fboundp 'file-remote-p) (efs-ftp-path file-name))
					    ^^^^^^^^^^^^
Oops! It's a typo. Must be:		    file-remote-p

> file-remote-p is defined in the dumped XEmacs, while
> this code thinks it is defined only if efs-ftp-path is also. I don't
> know enough about what is going on here to fix this. It seems
> rather strange to me that ediff should be loading efs or ange-ftp for
> a simple buffer compare. 

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.

	--michael  


