Pete Forman <[EMAIL PROTECTED]> writes:
> 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.
That's right. Hm. I'm not sure what to do about this. Hm. I'm
unsure whether the EFS team has done something about the
interoperability problem with rcp.el or not, and if they have done
something, what that might have been. Does anybody here have good
contact to the EFS people?
As a stopgap measure, I could put code in rcp.el which emits a warning
if efs is subsequently loaded. Something along the lines of:
(eval-after-load "efs" (error "EFS must be loaded before loading rcp.el!"))
What do you think?
I'm sorry that I haven't done something about rcp.el for such a long
time. It seems that the people who have problems with it are either
XEmacs users or NT users, or both. And since I use neither, I
sometimes have a little difficulty understanding where the problem
is. Okay, here's my resolve for the new year: try to understand the
problems of XEmacs and NT users with rcp.el and try to solve them
soon.
And I still haven't got around to the URL thing :-(
kai
--
A large number of young women don't trust men with beards. (BFBS Radio)
