Re: Git on macOS shows committed files as untracked

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




(Please no top-posting)
On 14/07/17 11:45, Elliot Chandler wrote:
For what it's worth, the file looks normal in Gentoo GNU/Linux (name appears "ḋἲ╓εﮯ𒑏○╓Ӳ" and it seems to work like any other directory).

Thanks for testing -
Normal and Normal ;-)
For me the 6th code point does look strange
The "box" with 04142F:
Code point 4142F is unassigned and is outside any currently defined block range.

So this is not valid Unicode, so we have a problem here under MacOS -
not much Git can do about it.



On Fri, Jul 14, 2017 at 4:41 AM, Torsten Bögershausen <tboegi@xxxxxx <mailto:tboegi@xxxxxx>> wrote:



    On 14/07/17 06:49, Lutz Roeder wrote:

        Using precomposeunicode still reproduces the issue:

        Repro steps:

        1. Download
        https://www.dropbox.com/s/0q5pbpqpckwzj7b/gitstatusrepro.zip?dl=0
        <https://www.dropbox.com/s/0q5pbpqpckwzj7b/gitstatusrepro.zip?dl=0>
        2. unzip gitstatusrepro.zip && cd gitstatusrepro
        3. git reset --hard
        4. git -c core.precomposeunicode=true status

        On branch master
        Untracked files:
            (use "git add <file>..." to include in what will be committed)


    A (short) investigation shows that this seems to be invalid unicode,
    at least from a MacOSX point of view ?

    Unzipping your repo shows this:
      git status -u
       deleted:
    "\341\270\213\341\274\262\342\225\223\316\265\357\256\257\360\222\221\217\342\227\213\342\225\223\323\262/test.txt"


    ===============
    If I run this:
      xx=$(printf
    "d\314\207\316\271\314\223\314\200\342\225\223\316\265\357\256\257\360\222\221\217\342\227\213\342\225\223\320\243\314\213/")

    echo   $xx | iconv -f UTF-8-MAC -t UTF-16 | xxd

    iconv: (stdin):1:5: cannot convert
    0000000: feff 1e0b 1f32 2553 03b5 fbaf            .....2%S....
    ===============================
    So I don't know if we can do something in Git to improve your repo.
    How did  you end up with such a directory name ?
    And would it be possible to rename it ?






[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux