Re: [Emacs-diffs] trunk r116230: Fix bug #16558 with w32-shell-execute on remote file names.

[Stefan Monnier]

> The problem that led me to introduce this call is that this succeeds:
>   (w32-shell-execute "open" "file")
> but this fails:
>   (w32-shell-execute "open" "dir/file")
> IOW, the DOCUMENT arg must either be an absolute file name, or live
> inside default-directory, not in one of its subdirectories.

Ah, that makes it more clear.  We should include this example in the comments.
It does beg the question: what does

   (w32-shell-execute "open" "dir/file")

do, then?  You say it "fails", but does it signal an error?  If so, why?
My world view is very POSIX-centric, so I'm probably missing the obvious.


        Stefan