Re: Git on Mac OS and precomposed unicode
- From
- Leo Koppelkamm <hello@leo-koppelkamm.de>
- Date
- Mar 21, 2013, 16:30 UTC
- Message-ID
- <E5C0B2ABD2EF46908D0711EF0C09817B@leo-koppelkamm.de>
- In-Reply-To
- <514B2F98.30409@web.de>
I found the problem: I copied the config out of your commit message, where you wrote core.precompose****d****unicode Turns out the d is too much. It seems to work now.
Leo
On Thursday, 21 March 2013 at 17:04, Torsten Bögershausen wrote:
Show 57 quoted lines
> 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