From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: git@vger.kernel.org
Subject: [BUG] 'ls-files path' fails if absolute path of workdir contains NFD (macOS)
Date: Tue, 30 Apr 2024 12:27:02 +0900 [thread overview]
Message-ID: <55D75808-70E0-46FA-906D-C00CD612A262@kba.biglobe.ne.jp> (raw)
On macOS, 'git ls-files path' does not work (gives an error)
if the absolute 'path' contains characters in NFD (decomposed).
I guess this is a (minor) bug of git.
[1] How to reproduce the problem
On macOS, git 2.39.3 or 2.45.0.219.gb9fe23f5ca(next branch),
file system can be APFS or HFS.
with zsh or bash:
% cd /somewhere # some safe place, /tmp or ~/tmp etc.
% mkdir $'u\xcc\x88' # ü in NFD
% cd ü # or cd $'u\xcc\x88' or cd $'\xc3\xbc'
% git init
% git ls-files $'/somewhere/u\xcc\x88' # NFD
fatal: /somewhere/ü: '/somewhere/ü' is outside repository at '/somewhere/ü'
% git ls-files $'/somewhere/\xc3\xbc' # NFC
(the same error as above)
In the 'fatal:' error message, there are three ü;
the 1st and 2nd are in NFC, the 3rd is in NFD.
[2] Some analysis
The path on the command line $'/somewhere/u\xcc\x88'
is converted to NFC by precompose_argv_prefix(),
called at git.c:451 in run_builtin().
But get_git_work_tree() (called at setup.c:50, in
abspath_part_inside_repo()) returns the work_tree in NFD,
and comparing it with the path in NFC (setup.c:92) fails.
I'm not familiar with git internals, but maybe
get_git_work_tree() should return NFC (on macoS)?
--
Jun (Jun-ichi Takimoto)
next reply other threads:[~2024-04-30 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 3:27 Jun T [this message]
2024-04-30 7:12 ` [BUG] 'ls-files path' fails if absolute path of workdir contains NFD (macOS) Torsten Bögershausen
2024-04-30 15:52 ` Jun. T
2024-04-30 16:58 ` Torsten Bögershausen
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=55D75808-70E0-46FA-906D-C00CD612A262@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--cc=git@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).