Ask HN: Git status, fatal iconv_open why? | Hacker News Reader

Ask HN: Git status, fatal iconv_open why?

2 pointsandrewfromx5 comments

git status

fatal: iconv_open(UTF-8,UTF-8-MAC) failed, but needed:

    precomposed unicode is not supported.

    If you want to use decomposed unicode, run

    "git config core.precomposeunicode false"

View on HN

I cite the git documentation: This option is only used by Mac OS implementation of Git. When core.precomposeUnicode=true, Git reverts the unicode decomposition of filenames done by Mac OS. This is useful when sharing a repository between Mac OS and Linux or Windows. (Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7). When false, file names are handled fully transparent by Git, which is backward compatible with older versions of Git

interesting. The only thing I was doing was:

import os

import uuid

from elevenlabs import VoiceSettings

from elevenlabs.client import ElevenLabs

running a python script with those inports in the directory. The python script makes a file but it's just a normal ascii name

It looks like ascii, but this doesn't mean programs don't receive the filename from the os in ascii.

what do you think caused this? I was minding my own business in a normal repo then all of a sudden

Is there anything in the full path to the repo that may have Unicode chars? Otherwise, use strace or similar on the git status command and examine the output of that.

Reply on news.ycombinator.com