Oh dear, look what I found in efs.el
;;;; ------------------------------------------------------------
;;;; Necessary overloads.
;;;; ------------------------------------------------------------
;;; The following functions are overloaded, instead of extended via
;;; the file-name-handler-alist. For various reasons, the
;;; file-name-handler-alist doesn't work for them. It would be nice if
;;; this list could be shortened in the future.
;; File name exansion. It is not until _after_ a file name has been
;; expanded that it is reasonable to test it for a file name handler.
(efs-overwrite-fn "efs" 'expand-file-name)
Where I thought I was looking at expand-file-name, I was actually in
efs-expand-file-name.
I suspect that the only way out of this is to customize the rcp
regexps to avoid the use of colons. The alternative is to throw some
more advice at efs. That looks like being a losing battle.
Perhaps we should accept that efs/ange-ftp has prior claim on its
entries in file-name-handler-alist. It is rather inelegant to rely on
efs and rcp being loaded in the right order.
Any suggestions for syntax? My first thought is to use semicolons
instead of colons. Something like a URI would have been nice but efs
would munch that up as well.
--
Pete Forman <mailto:[EMAIL PROTECTED]>
Western Geophysical Tel: + 44 1234 224798
Manton Lane, Bedford, MK41 7PA, UK Fax: + 44 1234 224804
<http://www.bedford.waii.com/wsdev/petef/PeteF_links.html>
