Re: Willing to debug bug #3542 (23.0.94; File access via UNC path slow again under Windows)

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: address@hidden,  address@hidden,  address@hidden,  address@hidden
> Date: Mon, 13 Jul 2009 08:17:08 -0400
> 
> > Already done by today's commits to the trunk.  The function is called
> > is_slow_fs, and returns non-zero if its argument resides on a
> > filesystem deemed slow.
> > I'm not sure this is what you want for file-remote-p.  Perhaps you
> > only want files on remote (a.k.a. networked) filesystems.  There's
> 
> I'm not sure I understand the difference.  Could you give an example of
> a filesystem that's slow but not "remote (a.k.a. networked)"?

The code in is_slow_fs considers only fixed disks and RAM disks not
``slow''.  Other types, which include CDs and removable media such as
USB memory sticks, are considered ``slow''.

> PS: the criterion for file-remote-p is (C-h f file-remote-p):
> "...A file is considered "remote" if accessing it is likely to be slower or
> less reliable than accessing local files..."

Right, but I remember a prolonged discussion about that which IIRC
ended in controversy.  That's why I asked.