Re: rssh.el interactions with ange-ftp/efs
>>>> On Fri, 15 Jan 1999 15:37:33 -0800,
>>>> bill(a)carpenter.ORG (WJCarpenter) said:
Again, see RFC-1738. I don't know what Netscape needs, but the
"~/"
in the above example is redundant (or might not even work) against
some servers. Do all servers support "CWD ~"?
No, but that's irrelevant anyway. EFS does all file name expansions
itself and talks to the server using only full path names. It defines
"~" to expand to whatever the server returned to pwd immediately after
connecting. This is part of the reason why a pwd is always executed
right after connecting. The other reason is to get the first piece of
information about the remote system type. SYST is often not supported
and sometimes lies.
What you get is more close to what you'd expect. You know, as if
the
people who wrote RFC-1738 were also FTP users. You log onto the
remote system using the user name and password. The first "/" is just
a delimiter telling you where the hostname stops. Things after that
are what you'd feed to FTP CWD (or "cd" in most ftp client
implementations). If you need to use a literal slash, it has to be
encoded using the usual URL encoding rules.
So, the answer to your original question is that there isn't a
special
syntax for things relative to your remote home directory. That's the
more or less default view. You could consider it to be a special
syntax to access absolute pathnames (you put a "%2f" where you'd
expect the root "/" to be).
Yuck! This is horrible syntax. I frequently use EFS to edit files as
root on the local host. In fact, since the null string for the
hostname defaults to the local host, then a quick edit of /etc/hosts
can be accomplished by editing /root＠:/etc/hosts. The RFC 1738 syntax
that you describe above would turn this into a mess.
...Sandy