Adrian Aichner <adrian(a)xemacs.org> writes:
But the example you comment as WRONG is exactly the behavior
documented in the substitute-in-file-name docstring in 21.5-b16:
If `/~' appears, all of FILENAME through that `/' is discarded.
Are you sure this is wrong?
[...]
I am not sure what we are seing is a bug unless the docstring is
alos a bug.
But that's the point, isn't it? Yes, substitute-in-file-name behaves
as documented, but I'm not convinced that such behavior is correct.
It certainly can't be right that you cannot find a file whose name
happens to begin with a tilde!
Maybe someone should ask the FSF maintainers what's their position on
this. Changing the behavior of substitute-in-file-name (or, for that
matter, read-file-name) is not something that should be done lightly.
expand-file-name explicitely refers to substitute-in-file-name.
Yes, but expand-file-name only expands *initial* "~/" and
"~username/", which is much better.