GNU bug report logs - #23902
25.1.50; Strange warning on string-collate-equalp's docstring

Previous Next

Full log

Message #26 received at 23902 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: oscarfv <at> telefonica.net (Óscar Fuentes)
Cc: michael_heerdegen <at> web.de, 23902 <at> debbugs.gnu.org
Subject: Re: bug#23902: 25.1.50;
 Strange warning on string-collate-equalp's docstring
Date: Wed, 06 Jul 2016 19:26:28 +0300

> From: oscarfv <at> telefonica.net (Óscar Fuentes)
> Cc: Michael Heerdegen <michael_heerdegen <at> web.de>,  23902 <at> debbugs.gnu.org
> Date: Wed, 06 Jul 2016 17:46:39 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> I also have trouble to understand.  How can I compare file names modulo
> >> collate-equality, if not with this function?
> >
> > With string=, of course.  (Or, better yet, with file-equal-p, but
> > that's a different story.)
> 
> I understand why comparing file names with string-collate-equalp is a
> bad idea (it can return t for cases where the names are different from
> the POV of the file system) but then explaining this in full and
> pointing to file-equal-p doesn't take too much space (about the same as
> the current note, I'll say).

If you think adding that will make the issue more clear, go ahead and
propose or push a patch.

> (using string= for comparing file names is a bad idea for the same
> reason idea when the FS is case-insensitive, BTW)

Which is why I mentioned file-equal-p.

> Putting notes about non-existing issues is surely confusing, isn't it?

Indeed.  But this issue does exist, and is real.  See, for example:

  http://archives.miloush.net/michkap/archive/2005/10/17/481600.html

(CompareString is what we use on MS-Windows to implement
string-collate-equalp and string-collate-lessp.)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.