Re: file-relative-name and remote files

[Kai Großjohann]

Richard Stallman <address@hidden> writes:

> Hmm, this raises the issue of what expand-file-name should do with
> "/foo:../..".  I guess it must leave that unchanged, which means that
> the expand-file-name handler for these file names should be rather
> careful in what it does to simplify whatever part of the name comes
> after.  It is not correct to simplify /X/../Y into /Y when /X
> is a remote prefix.

Actually, what Tramp does to expand "/foo:../.." is the following:

* The localname part ("../..") is not absolute, so it must be relative
  to the remote home dir.  Prepend "~/" to the localname, giving
  "/foo:~/../..".

* Expand tildes, giving, say, "/foo:/home/jrl/../..".

* Expand the localname part, giving "/", then tack on the prefix.

The final result is "/foo:/".

Is this the right behavior so far?



In the case of "/address@hidden:../..", where the ~root on the remote host
is "/root", the result will be "/address@hidden:/..", which is not pretty.
Maybe this should be expanded, again, to "/".  WDYT?

-- 
A preposition is not a good thing to end a sentence with.