rssh.el interactions with ange-ftp/efs

Kai.Grossjohann(a)CS.Uni-Dortmund.DE writes: Hello Kai, I was looking (casually) into rssh.el today and although I didn't get it working (I do not know yet what caused it, sorry) I do have a proposal for you. Kai, may I suggest you change file names used to access rssh.el? I am also CC'ing some people involved in this as I also have a general suggestion. Currently you have for sssh.el paths /s:bblabla＠blabla:path the problem is that this also matches the efs path regexp. I haven't checked but it probably clashes with ange-ftp too. So if efs gets loaded (possibly automatically) after rssh.el has been installed the efs handler picks up the sssh path and complains. So after inspecting the regexps used I suggest you use something like /::xsh:user＠host:path (EFS paths cannot start with a colon) Ugly you say? Read on. However I suggest we go even further. What you really want is that the user simply times /user＠host:path and that Emacs figures out with remote access mechanism to use ( you have a variably remote-path-xsh-hosts or something like that). So I propose that a A. a new set of remote path names is introduced, which uniquely identifies the access method /::method:<method-specific-info> i.e. /::xsh:user＠host:path always uses Kai's stuff /::ftp:user＠host:path always EFS/ange-ftp In the future a http access method could be added etc. B. The general /user＠host:path remote filename specification is handled by a wrapper that decides what methods to use, based on specific values of user, host and path. C. file-remote-p and similar (if available) is changed to include the new types introduced by A. Jan P.S. The handler in B could even decide to just load the file if it is on a path that is also mounted on this machine.