Git development
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Leo Koppelkamm <hello@leo-koppelkamm.de>
Cc: git@vger.kernel.org, "Torsten Bögershausen" <tboegi@web.de>
Subject: Re: Git on Mac OS and precomposed unicode
Date: Thu, 21 Mar 2013 17:04:40 +0100	[thread overview]
Message-ID: <514B2F98.30409@web.de> (raw)
In-Reply-To: <64B4EB934AFE4B358B94EB717103887E@leo-koppelkamm.de>

On 21.03.13 14:00, Leo Koppelkamm wrote:
> Torsten Bögershausen added a patch for this a while ago.
> It seems it only works for files, not for folders with unicode in it.
>
> Eg. on ubuntu box:
> git init
> mkdir hä
> touch hä/file
> git add hä
> git commit 
>
> Later on Mac
> git clone ………
> git status
>
> # On branch master 
> # Untracked files: 
> # (use "git add <file>..." to include in what will be committed) 
> # 
> # hä/
>
> Regards Leo
That is what I read from the commit message:

   When creating a new git repository with "git init" or "git clone",
    "core.precomposedunicode" will be set "false".
   
    The user needs to activate this feature manually.  She typically
    sets core.precomposedunicode to "true" on HFS and VFAT, or file
    systems mounted via SAMBA.

(Which is slighty wrong, because the name of the config variable
is core.precomposeunicode)

What does
git config core.precomposeunicode
say ?

You may consider to set it to set it to true globally,
git config --global core.precomposeunicode true,
and the next "git clone" will work as expected.

On the other hand,
could/should we consider to change the default to true in Git 2.0?

HTH
/Torsten



 






What does git config

       reply	other threads:[~2013-03-21 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <64B4EB934AFE4B358B94EB717103887E@leo-koppelkamm.de>
2013-03-21 16:04 ` Torsten Bögershausen [this message]
2013-03-21 16:30   ` Git on Mac OS and precomposed unicode Leo Koppelkamm

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=514B2F98.30409@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=hello@leo-koppelkamm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox