From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org, Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: [PATCH] completion: add and use the __git_get_config_subsection helper function
Date: Tue, 14 Nov 2023 10:08:46 +0900 [thread overview]
Message-ID: <xmqqzfzh16qp.fsf@gitster.g> (raw)
In-Reply-To: <20231113222528.62771-1-szeder.dev@gmail.com> ("SZEDER Gábor"'s message of "Mon, 13 Nov 2023 23:25:27 +0100")
SZEDER Gábor <szeder.dev@gmail.com> writes:
> +# Lists all subsections in the given section which contain the given
> +# config variable, with the section and variable names removed.
> +__git_get_config_subsections ()
> +{
> + local section="$1" var="$2" i IFS=$'\n'
> + for i in $(__git config --name-only --get-regexp "^$section\..*\.$var$"); do
> + i=${i#$section.}
> + i=${i%.$var}
As this script is allowed bash-isms, I wondered if we can use
a single pattern substitution instead of two remove pre/suffix
pattern substitution, but I guess it would not work, and the above
is perfectly readable.
> + echo "$i"
As the subsection is designed to contain unbounded set of end-user
controlled names, we probably should do
printf "%s\n" "$i"
instead to protect us from interesting names (e.g. ones that begin
with a dash).
> + done
> +}
Interesting to see that we do not need to bother deduplicating the
output from here.
> diff --git a/t/t9902-completion.sh b/t/t9902-completion.sh
> index a7c3b4eb63..11ed83d0ed 100755
> --- a/t/t9902-completion.sh
> +++ b/t/t9902-completion.sh
> @@ -2130,6 +2130,19 @@ test_expect_success '__git_get_config_variables' '
> test_cmp expect actual
> '
>
> +test_expect_success '__git_get_config_subsections' '
> + cat >expect <<-\EOF &&
> + subsection-1
> + SubSection-2
> + sub.section.3
> + EOF
> + test_config interesting.subsection-1.name good &&
> + test_config Interesting.SubSection-2.Name good &&
> + test_config interesting.sub.section.3.name good &&
> + __git_get_config_subsections interesting name >actual &&
> + test_cmp expect actual
> +'
Good to see an uppercase character is used here ;-).
Thanks.
next prev parent reply other threads:[~2023-11-14 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 22:25 [PATCH] completion: add and use the __git_get_config_subsection helper function SZEDER Gábor
2023-11-14 1:08 ` Junio C Hamano [this message]
2023-11-28 12:40 ` SZEDER Gábor
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=xmqqzfzh16qp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=levraiphilippeblain@gmail.com \
--cc=szeder.dev@gmail.com \
/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).