From: oscarfv@telefonica.net (Óscar Fuentes)
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, 23902@debbugs.gnu.org
Subject: bug#23902: 25.1.50; Strange warning on string-collate-equalp's docstring
Date: Wed, 06 Jul 2016 19:44:50 +0200 [thread overview]
Message-ID: <87k2gyek4t.fsf@wanadoo.es> (raw)
In-Reply-To: <838txen363.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 06 Jul 2016 19:26:28 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
What about replacing the paragraph with this one:
Note that this function is not adequate for testing if two strings
name the same file. Use `file-equal-p' for that purpose.
?
next prev parent reply other threads:[~2016-07-06 17:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 22:05 bug#23902: 25.1.50; Strange warning on string-collate-equalp's docstring Óscar Fuentes
2016-07-06 14:34 ` Eli Zaretskii
2016-07-06 15:08 ` Michael Heerdegen
2016-07-06 15:28 ` Eli Zaretskii
2016-07-06 15:46 ` Óscar Fuentes
2016-07-06 16:26 ` Eli Zaretskii
2016-07-06 17:44 ` Óscar Fuentes [this message]
2016-07-06 18:32 ` Eli Zaretskii
2016-07-09 17:06 ` Glenn Morris
2016-07-09 17:21 ` Eli Zaretskii
2016-07-09 21:36 ` Óscar Fuentes
2016-07-10 2:40 ` Eli Zaretskii
2016-07-10 3:06 ` Michael Heerdegen
2016-07-10 14:40 ` Eli Zaretskii
2016-07-06 15:55 ` Michael Heerdegen
2016-07-06 16:30 ` Eli Zaretskii
2016-07-06 16:44 ` Michael Heerdegen
2016-07-06 17:18 ` Eli Zaretskii
2016-07-06 22:49 ` Michael Heerdegen
2016-07-07 2:38 ` Eli Zaretskii
2016-07-07 21:52 ` Michael Heerdegen
2016-07-08 10:11 ` Eli Zaretskii
2016-07-08 20:59 ` Michael Heerdegen
2016-07-09 6:52 ` Eli Zaretskii
2016-07-09 17:06 ` Richard Stallman
2016-07-09 22:59 ` Michael Heerdegen
2016-07-06 15:48 ` Glenn Morris
2016-07-06 16:27 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2gyek4t.fsf@wanadoo.es \
--to=oscarfv@telefonica.net \
--cc=23902@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).