From: Philipp Stephani <p.stephani2@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: 30350@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
Mikhail Gusarov <dottedmag@dottedmag.net>
Subject: bug#30350: Build breakage of master on MacOS 10.13
Date: Tue, 06 Feb 2018 21:15:32 +0000 [thread overview]
Message-ID: <CAArVCkTBSF+dvdBOZ_G9ryvBdQoY9_RE1aGJUvbmD_LL2ZnO-g@mail.gmail.com> (raw)
In-Reply-To: <20180206185610.GA97455@breton.holly.idiocy.org>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
Alan Third <alan@idiocy.org> schrieb am Di., 6. Feb. 2018 um 19:56 Uhr:
> On Tue, Feb 06, 2018 at 04:27:40PM +0100, Mikhail Gusarov wrote:
> > Yes, it is. I can't find the relevant sources right away, but opening a
> > file inside a file is a syntax for opening resource forks under OS X,
> > so `/foo/bar/baz/.` is a "directory" of resource forks there. This
> > syntax is not likely to go away anytime soon.
>
> Hmm, perhaps this method of checking for a directory just won’t ever
> work reliably on macOS then.
>
>
But it works reliable in all isolated test cases that I've tried. Only the
combination with call-process seems to cause issues for some weird reason.
[-- Attachment #2: Type: text/html, Size: 999 bytes --]
next prev parent reply other threads:[~2018-02-06 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 6:31 Build breakage of master on MacOS 10.13 Mikhail Gusarov
2018-02-06 8:08 ` Philipp Stephani
2018-02-06 15:27 ` bug#30350: " Mikhail Gusarov
2018-02-06 17:40 ` John Wiegley
2018-02-06 21:26 ` Mikhail Gusarov
2018-02-06 21:29 ` Philipp Stephani
2018-02-06 21:31 ` Mikhail Gusarov
2018-02-06 21:30 ` Mikhail Gusarov
2018-02-06 18:56 ` Alan Third
2018-02-06 21:15 ` Philipp Stephani [this message]
2018-02-06 21:14 ` Philipp Stephani
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=CAArVCkTBSF+dvdBOZ_G9ryvBdQoY9_RE1aGJUvbmD_LL2ZnO-g@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=30350@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=dottedmag@dottedmag.net \
--cc=eggert@cs.ucla.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 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.