Re: testing for a remote file to include file on a Windows mapped drive

[Stefan Monnier]

> I have some code that needs to avoid some particular processing when the
> current input might name a remote file. I don't want the code to try to
> contact anything remote in this case.

> In Windows, you can map a remote directory to a virtual drive. So, for
> instance, "h:foo" or "h:/foo" might represent a remote file. But the same
> name would represent a local file if drive `h' is local, not mapped.

The same problem exists under GNU/Linux and friends.
~/foo might be a mount point and all files underneath are access via NFS
or SSHFS (or whatever else).

Under GNU/Linux, I believe there are C-level primitives that can help
figure out whether a file is really local or not, so we could use those
to improve file-remote-p.


        Stefan