emacsclient x:foo

[Juanma Barranquero]

I've just commited a change to emacsclient on Windows so

  X:foo

which was until now understood to be a NTFS filestream, it is now interpreted as

  X:/current-directory-on-drive-X/foo

That is more consistent with most programs on Windows, and much more
user friendly (NTFS streams are not often used directly by the user,
while drive-relative filenames are common).

For simplicity, I've processed all relative paths (not just X:foo, but
foo and .\foo and ./foo, for example) through the GetFullPathName API.
AFAICS, that improves consistency; cases where previously Emacs
received X:\foo/bar will now be X:\foo\bar. Absolute paths, like
X:/foo/bar, are still passed unscathed.

All this preamble is to ask: if someone is using a Windows emacsclient
to connect to non-Windows Emacs servers, I'd like to know of any
regressions with respect to filename handling.

Thanks,

             Juanma