git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Manuel Boni via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Manuel Boni" <ziosombrero@gmail.com>
Subject: Re: [PATCH] config.txt: add completion for include, includeIf
Date: Wed, 13 Jul 2022 12:52:27 -0700	[thread overview]
Message-ID: <xmqqv8s0bxj8.fsf@gitster.g> (raw)
In-Reply-To: <pull.1285.git.1657738937049.gitgitgadget@gmail.com> (Manuel Boni via GitGitGadget's message of "Wed, 13 Jul 2022 19:02:16 +0000")

"Manuel Boni via GitGitGadget" <gitgitgadget@gmail.com> writes:

> From: Manuel Boni <ziosombrero@gmail.com>
>
> Git config's tab completion does not yet know about the "include"
> and "includeIf" sections, nor the related "path" variable.
>
> Add tab completion support for the aforementioned items,
> along with two new tests, based on the existing ones,
> specifically for this completion. Variable completion only works
> for "include" for now.

You may have started this work for tab completion, but I think you
should describe it as adding missing documentation (this comment
extends to the title of the patch, too).  The work to teach "tab
completion" about the variables "git config" can take has done long
time ago, and the work by this patch to add description for
<include> and <includeIf> is used as an input to that previous work,
which results in "git config inc<TAB>" to be command line completed.

> Credit for the ideas behind this patch goes to
> Ævar Arnfjörð Bjarmason.
>
> Signed-off-by: Manuel Boni <ziosombrero@gmail.com>
> Based-on-patch-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>

The order of these two is backwards, no?  Ævar may have written
something that inspire you to arrive at this version, which you
signed off before sending it out.

> +include.path::
> +
> +includeIf.<condition>.path::

Losing the extra blank line will make it clearer, if your intention
is that the next lines apply to both of the above two.

> +	Special variables to include other configuration files. See
> +	the "CONFIGURATION FILE" section in the main
> +	linkgit:git-config[1] documentation.

Thanks.

  parent reply	other threads:[~2022-07-13 19:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 19:02 [PATCH] config.txt: add completion for include, includeIf Manuel Boni via GitGitGadget
2022-07-13 19:32 ` Jeff King
     [not found]   ` <d21115d5-8bae-c120-453f-9dbb600d0431@gmail.com>
2022-07-14 21:13     ` Jeff King
2022-07-13 19:52 ` Junio C Hamano [this message]
2022-07-16 20:13 ` [PATCH v2] config.txt: document " Manuel Boni via GitGitGadget
2022-07-16 22:49   ` Jeff King

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=xmqqv8s0bxj8.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=ziosombrero@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).