From: "Rubén Justo" <rjusto@gmail.com>
To: Britton Kerin <britton.kerin@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH v2 1/1] completion: dir-type optargs for am, format-patch
Date: Thu, 29 Feb 2024 01:04:36 +0100 [thread overview]
Message-ID: <6683f24e-7e56-489d-be2d-8afe1fc38d2b@gmail.com> (raw)
In-Reply-To: <CAC4O8c9z4s4fFU6_h6ZRBnDhZyiTp3XR8j0DrARj+1SauLbQEQ@mail.gmail.com>
On Mon, Feb 12, 2024 at 13:52:53 -0900, Britton Kerin wrote:
> __git_complete_dir ()
> {
> local cur_="$cur"
>
> while test $# != 0; do
> case "$1" in
> --cur=*) cur_="${1##--cur=}" ;;
> *) return 1 ;;
> esac
> shift
> done
>
> # This rev-parse invocation amounts to a pwd which respects -C options
> local context_dir=$(__git rev-parse --show-toplevel
> --show-prefix 2>/dev/null | paste -s -d '/' 2>/dev/null)
> [ -d "$context_dir" ] || return 1
>
> compopt -o noquote
>
> local IFS=$'\n'
> local unescaped_candidates=($(cd "$context_dir" 2>/dev/null &&
> compgen -d -S / -- "$cur_"))
> for ii in "${!unescaped_candidates[@]}"; do
> COMPREPLY[$ii]=$(printf "%q" "${unescaped_candidates[$ii]}")
> done
> }
>
> This one works for all weird characters that I've tried in bash 5.2 at
> least, and in frameworks that do their own escaping also (e.g.
> ble.sh). Since your advice so far was so good I thought I'd ask if
> there is anything obvious to you that is still wrong here?
> If not I guess what's left is special code to make it work better with
> old versions of bash. I'm a little sceptical that this is worth it
> since bash 5 is already 5 years old and it's only completion code
> we're talking about but I guess it could be done.
I don't think you need to dig too much into old Bash versions. If it
works with a recent one, it's a good start.
Have you considered adding some tests to t/t9902-completion.sh?
It is desirable to see some tests at least for __git_complete_dir.
Perhaps it would also help you to polish the function.
Sorry for the late response. I just found your message while reviewing
the topics in the 'What's cooking'.
prev parent reply other threads:[~2024-02-29 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 21:41 [PATCH 0/1] completion: complete dir-type option args to am, format_patch Britton Leo Kerin
2024-01-09 0:53 ` [PATCH v2 " Britton Leo Kerin
[not found] ` <20240109005303.444932-1-britton.kerin@gmail.com>
2024-01-09 0:53 ` [PATCH v2 1/1] completion: dir-type optargs for am, format-patch Britton Leo Kerin
2024-02-03 15:13 ` Rubén Justo
2024-02-13 0:52 ` Britton Kerin
2024-02-29 0:04 ` Rubén Justo [this message]
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=6683f24e-7e56-489d-be2d-8afe1fc38d2b@gmail.com \
--to=rjusto@gmail.com \
--cc=britton.kerin@gmail.com \
--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 NNTP newsgroup(s).