zsh-workers
 help / color / mirror / code / Atom feed
From: "Jun. T" <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: Bug report; git tab-completion on macOS within paths containing unicode characters
Date: Tue, 30 Apr 2024 02:37:45 +0900	[thread overview]
Message-ID: <EE8B9075-8D7A-43A9-9745-662F40B31519@kba.biglobe.ne.jp> (raw)
In-Reply-To: <CAH+w=7bqvSC_dRuNJw6i=MeHeKAvjj_wTQXvkkgHLPyVvQRMjg@mail.gmail.com>


> 2024/04/29 4:01、Bart Schaefer <schaefer@brasslantern.com>のメール:
> 
> <__git_files.txt>

With this patch, 'git add t<TAB>' apparently works, but
_complete_debug indicates that the problem still remains.

In __git_files (called from __git_other_files), 'git ls-files'
is called two times.
The first one is (omitting a few irrelevant options):
    git ls-files --others -- ':\(icase\)\''/path/to/ü/test2/t\''\*'
and this gives nothing (no files, no error messages).
Then __git_files tries the second call:
    git ls-files --others --
and this returns 'test.txt'. But this returns only the files in
the current directory and its subdirectories. So if we are in a
subdirectory then files in the top directory are not listed.

I tried
    git ls-files path
with path in both in NFC and NFD (by using $'\x..'), but both
didn't work.
I guess this is a problem of git itself.

  reply	other threads:[~2024-04-29 17:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  7:17 Yves Delley
2024-04-27 19:14 ` Bart Schaefer
2024-04-27 19:31   ` Bart Schaefer
2024-04-28  7:22     ` Yves Delley
2024-04-28 15:28       ` Bart Schaefer
2024-04-28 18:59         ` Bart Schaefer
2024-04-28 19:01           ` Bart Schaefer
2024-04-29 17:37             ` Jun. T [this message]
2024-04-29 17:54               ` Bart Schaefer
2024-04-30  0:41                 ` Jun. T
2024-04-30  1:57                   ` Bart Schaefer
2024-04-30  2:31                     ` Jun. T

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=EE8B9075-8D7A-43A9-9745-662F40B31519@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).