From: Michael Albinus <michael.albinus@gmx.de>
To: Ken Brown <kbrown@cornell.edu>
Cc: 32246@debbugs.gnu.org
Subject: bug#32246: 27.0.50; files-tests failure on Cygwin
Date: Thu, 26 Jul 2018 15:56:04 +0200 [thread overview]
Message-ID: <87fu06w16z.fsf@gmx.de> (raw)
In-Reply-To: <87va93qkxk.fsf@gmx.de> (Michael Albinus's message of "Wed, 25 Jul 2018 19:33:59 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Ken,
>> No, that code is a fallback that is only relevant if the call to
>> pathconf with _PC_CASE_INSENSITIVE fails or can't be made. See the
>> comment at the beginning of the definition of
>> file_name_case_insensitive_p, and also the comment before the
>> definition.
>
> OK, so I will continue to debug.
It looks that on cygwin, file-name-case-insensitive-p returns different
values for existing and non-existing files:
--8<---------------cut here---------------start------------->8---
M-! touch /tmp/foo
(file-name-case-insensitive-p "/tmp/foo")
=> nil
(file-name-case-insensitive-p "/tmp/bar")
=> t
--8<---------------cut here---------------end--------------->8---
The doc of file-name-case-insensitive-p does not require that FILENAME exists.
>> Best regards,
>>
>> Ken
Best regards, Michael.
next prev parent reply other threads:[~2018-07-26 13:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-22 18:10 bug#32246: 27.0.50; files-tests failure on Cygwin Ken Brown
2018-07-22 18:23 ` Michael Albinus
2018-07-23 17:01 ` Ken Brown
2018-07-25 12:00 ` Michael Albinus
2018-07-25 13:37 ` Ken Brown
2018-07-25 16:46 ` Michael Albinus
2018-07-25 16:56 ` Ken Brown
2018-07-25 17:33 ` Michael Albinus
2018-07-26 13:56 ` Michael Albinus [this message]
2018-07-26 14:54 ` Ken Brown
2018-07-26 15:03 ` Michael Albinus
2018-07-27 18:34 ` Ken Brown
2018-07-27 19:30 ` Michael Albinus
2018-07-27 20:30 ` Ken Brown
2018-07-27 21:10 ` Eli Zaretskii
2018-07-27 21:32 ` Ken Brown
2018-07-27 21:34 ` Ken Brown
2018-07-26 17:38 ` Eli Zaretskii
2018-07-27 15:27 ` Michael Albinus
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=87fu06w16z.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=32246@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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).