From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Eglen <sje30@cam.ac.uk>
Cc: sje30@cam.ac.uk, 56443@debbugs.gnu.org, mardani29@yahoo.es
Subject: bug#56443: 28.1; Mac segmentation fault with ffap
Date: Fri, 08 Jul 2022 13:47:31 +0300 [thread overview]
Message-ID: <83czef51a4.fsf@gnu.org> (raw)
In-Reply-To: <m2wncnudfd.fsf@blur.lan> (message from Stephen Eglen on Fri, 08 Jul 2022 11:02:20 +0100)
> From: Stephen Eglen <sje30@cam.ac.uk>
> Cc: Eli Zaretskii <eliz@gnu.org>, sje30@cam.ac.uk, 56443@debbugs.gnu.org
> Date: Fri, 08 Jul 2022 11:02:20 +0100
>
> Thanks everyone for help debugging this.
>
> > BTW, I don't really understand the semantics of
> > file-name-case-insensitive-p. The docstring says that it returns nil if
> > the file is not found, but these calls return t on my system:
> >
> > (file-name-case-insensitive-p "")
> > (file-name-case-insensitive-p "FileThatDoesNotExist")
>
> I also find that those two expressions return t on my mac, and nil on my
> linux machine. This seems to be consistent with the doc string:
>
>
> Return t if file FILENAME is on a case-insensitive filesystem. Return
> nil if FILENAME does not exist or is not on a case-insensitive
> filesystem, or if there was trouble determining whether the filesystem
> is case-insensitive.
>
> It returns t on mac as it is case-insensitive by default, presumbly
> irrespective of whether the file exists.
>
> One small suggestion for the docstring might be to remove the double
> negative in the second sentence:
>
> "is not on a case-insensitive filesystem"
>
> could be
>
> "is on a case-sensitive filesystem"
No, that's not accurate either. What we need to say that if the file
doesn't exist, we _might_ return nil, unless it's known in advance
that _all_ filesystems are case-insensitive.
next prev parent reply other threads:[~2022-07-08 10:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 17:18 bug#56443: 28.1; Mac segmentation fault with ffap Stephen Eglen
2022-07-07 20:36 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-08 5:39 ` Eli Zaretskii
2022-07-08 9:54 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-08 10:02 ` Stephen Eglen
2022-07-08 10:47 ` Eli Zaretskii [this message]
2022-07-08 9:35 ` Mattias Engdegård
2022-07-08 10:45 ` Eli Zaretskii
2022-07-08 13:14 ` Mattias Engdegård
2022-07-08 16:12 ` Stephen Eglen
2022-07-08 16:15 ` Mattias Engdegård
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czef51a4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56443@debbugs.gnu.org \
--cc=mardani29@yahoo.es \
--cc=sje30@cam.ac.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.