From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>,
Andreas Schwab <schwab@linux-m68k.org>,
Paul Eggert <eggert@cs.ucla.edu>
Cc: p.stephani2@gmail.com, 48471@debbugs.gnu.org, larsi@gnus.org,
monnier@IRO.UMontreal.CA
Subject: bug#48471: 28.0.50; Incorrect handling of `project-ignores' on macOS (BSD find?) if project root is a directory name
Date: Sun, 30 May 2021 14:14:45 +0300 [thread overview]
Message-ID: <19304fec-2bb1-1cbb-3e58-177537981911@yandex.ru> (raw)
In-Reply-To: <83r1ho4tr7.fsf@gnu.org>
On 30.05.2021 09:31, Eli Zaretskii wrote:
> It's in Posix, but I'm not sure how portable it is in practice. Paul,
> Andreas, do you happen to know?
>
> Perhaps for 100% portability we should probe for its support?
Since even the ancient BSD find on Macs supports it, I figured it's
widespread enough. But if people say otherwise, I suppose we could add a
probe.
next prev parent reply other threads:[~2021-05-30 11:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 20:05 bug#48471: 28.0.50; Incorrect handling of `project-ignores' on macOS (BSD find?) if project root is a directory name Philipp
2021-05-17 0:23 ` Dmitry Gutov
2021-05-17 19:37 ` Philipp
2021-05-17 20:02 ` Philipp
2021-05-17 23:06 ` Dmitry Gutov
2021-05-23 11:08 ` Philipp
2021-05-29 21:44 ` Dmitry Gutov
2021-05-30 4:29 ` Lars Ingebrigtsen
2021-05-30 11:13 ` Dmitry Gutov
2021-05-31 5:33 ` Lars Ingebrigtsen
2021-05-30 6:31 ` Eli Zaretskii
2021-05-30 11:14 ` Dmitry Gutov [this message]
2021-05-30 16:27 ` Paul Eggert
2021-05-30 16:36 ` Eli Zaretskii
2021-06-07 1:58 ` Dmitry Gutov
2021-06-07 8:51 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-07 18:48 ` Philipp
[not found] ` <ff528f00-ac80-4a84-fafb-076896793930@yandex.ru>
2021-10-09 22:14 ` Paul Eggert
[not found] ` <4de8fa95-e8f3-d07f-2f0c-8b06feff7190@cs.ucla.edu>
2021-10-09 22:29 ` Dmitry Gutov
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=19304fec-2bb1-1cbb-3e58-177537981911@yandex.ru \
--to=dgutov@yandex.ru \
--cc=48471@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=p.stephani2@gmail.com \
--cc=schwab@linux-m68k.org \
/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.