"Tom Roche" <[EMAIL PROTECTED]> writes:
> [...] It'd be nice if the user could specify (perhaps even by
> server) a sequence of preferred transports. E.g. for ssh.ncsu.edu I
> want only to transfer via scp; for ftp.ncs.ncsu.edu I want to
> transfer via scp but will transfer via ftp if that fails; for some
> box on (presumably secure :-) my switched office LAN I'll transfer
> by any means available. Then rcp.el could try the first preference,
> and on failure try the next, and recurse. (Or something like that
> :-)
My personal opinion is that this is not worthwhile, really. rcp.el
file names are so long already, that trying to shorten them by 4
characters is not really going to win much.
You may wish to use bookmarks (C-x r m and C-x r b are your friends)
or environment variables to shorten file names. I have also been
thinking of abbreviations for file names, but haven't gotten very far
with that.
> Note that my _personal_ top priority is just getting scp or SSH
> transfer working on Win32, though. DO THAT FIRST !-)
Joe Stoy has done some work in this area, but I don't have W32, so I
can't check what works and what doesn't.
I have tried to incorporate all changes to rcp.el which are necessary
for ssh on W32, but Joe reports that it is also necessary to patch
ssh.c and/or scp.c to work correctly on W32. You should be able to
find relevant things in the mailing list archive at www.mailarchive.com.
kai
--
Beware of flying birch trees.
