All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Jeff King <peff@peff.net>, roeder.git@mailnull.com, git@vger.kernel.org
Subject: Re: Git on macOS shows committed files as untracked
Date: Thu, 13 Jul 2017 12:35:50 -0700	[thread overview]
Message-ID: <xmqq60eww2nd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <130b338b-2e77-65d6-a3fa-f272ac43b81c@web.de> ("Torsten Bögershausen"'s message of "Thu, 13 Jul 2017 10:42:29 +0200")

Torsten Bögershausen <tboegi@web.de> writes:

> Thanks for the fast analyzes -
> in short:
> what does
> git -c core.precomposeunicode=true status
> say ?
>
> The easiest thing may be to set
> git config --global core.precomposeunicode true

Good suggestion.

I learned a new thing today.  I somehow thought that precompose
trick was only about argv[] when a program starts up and did not
apply to paths readdir(3) finds through dir.c, e.g.

    $ git add .

But apparently there is replacement readdir() used in compat/ for
MacOSX so the paths from the system are also covered by the
configuration.

  reply	other threads:[~2017-07-13 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 22:21 Git on macOS shows committed files as untracked roeder.git
2017-07-12 23:15 ` Jeff King
2017-07-13  8:42   ` Torsten Bögershausen
2017-07-13 19:35     ` Junio C Hamano [this message]
     [not found] <CANmutwCSGgLxESPmTJZXkid6P1N6HwwOTaz=7QHOsSPrrHQ4EQ@mail.gmail.com>
2017-07-14  4:51 ` Lutz Roeder
2017-07-14  8:41 ` Torsten Bögershausen
2017-07-14  9:46   ` Elliot Chandler
     [not found]   ` <CAHVrscDg8bc-CYm6dSJFgdPSv1vJ0=AC0s3y26CHctKkYAvJyA@mail.gmail.com>
2017-07-14 12:35     ` Torsten Bögershausen
2017-07-14 13:28       ` Jeff King
2017-07-14 13:29       ` Andreas Schwab

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=xmqq60eww2nd.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=roeder.git@mailnull.com \
    --cc=tboegi@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. 
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.