"João Távora" <address@hidden> writes:
> I've only now caught up with the discussion of bug#33255. Are the
> consequences of interpreting the string "c:" on Windows as a relative
> file name understood?
>
> With HOME="z:", it used to be that (expand-file-name "~/blabla")
> returned "z:/blabla" but now it returns
> "z:/source/emacs/emacs/src/z:/blabla", which is not a valid Windows
> pathname.
[snip]
I was about to post a reply but Yuri already answered, so I'll only add
a pointer to an official reference about this topic:
https://docs.microsoft.com/en-us/dotnet/standard/io/file-path-formats
Óscar, I get it that z:bla has a meaning. But is this meaning ever useful when for expanding "~/bla"?
I didn't say the change was "wrong".
I just asked, basically:
* if anyone had contemplated this particular problem on Windows;
* if it's possible to interpret HOME specially for this particular bit of backward compatibility without breaking the cases of bug#33255
João Távora