Subject: Re: bug#23902: 25.1.50; Strange warning on string-collate-equalp's docstring

From: Eli Zaretskii <[email-masked]>
Date: Sun, 10 Jul 2016 17:40:10 +0300

> From: Michael Heerdegen <[email-masked]>
> Cc: [email-masked] (Óscar Fuentes),
>   [email-masked]
> Date: Sun, 10 Jul 2016 05:06:49 +0200
> 
> Eli Zaretskii <[email-masked]> writes:
> 
> > > I think that Glenn is saying that you can compare file names for other
> > > purposes than knowing if they name the same file.
> >
> > Then it's not "equality", it's "equivalence".
> 
> Equivalence implies equality of equivalence classes.

I think we shouldn't split hair on this matter.  File-name equality is
something that doesn't need explanation, and we don't want to muddy
the waters by looking how to confuse matters even more.

> Does `file-equal-p' test whether the files named by the strings are
> equal, or whether these strings name the same file and are thus
> equivalent

IIUC, it does neither (e.g., because it supports links and other
stuff).

Now, can we please move on to more important things?