Re: (expand-file-name "/..")

Mats Lidell writes:

 > On the subject of twisty-little-functions-all-alike -- How does all of
 > this relate to file-truename which doesn't seem to have the flaw(!?) 
 > as described above!?

file-truename actually follows the path on the device.  See
realpath(1) and realpath(3) man pages.  Unlike the system utilities,
however, file-truename only follows the actual path until it ends on
the device, then appends any components remaining in the given name.

expand-file-name, file-name-as-directory, and similar functions
manipulate strings, and so won't necessarily correspond to any real
directory entries (they might contain symlinks, as well as the
occasional anomolous "/..").