From: Phillip Wood <phillip.wood123@gmail.com>
To: Derrick Stolee <derrickstolee@github.com>,
Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: gitster@pobox.com, johannes.schindelin@gmx.de,
Jeff King <peff@peff.net>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [Patch v2 2/2] add: test use of brackets when color is disabled
Date: Wed, 7 Jun 2023 16:31:12 +0100 [thread overview]
Message-ID: <2143c98e-238b-8edc-a16c-be448a8b56e8@gmail.com> (raw)
In-Reply-To: <281431b8-af40-9de9-f4b4-c596c5dbb3af@github.com>
Hi Stolee
On 07/06/2023 14:44, Derrick Stolee wrote:
> From 02156b81bbb2cafb19d702c55d45714fcf224048 Mon Sep 17 00:00:00 2001
> From: Derrick Stolee <derrickstolee@github.com>
> Date: Wed, 7 Jun 2023 09:39:01 -0400
> Subject: [PATCH v2 2/2] add: test use of brackets when color is disabled
>
> The interactive add command, 'git add -i', displays a menu of options
> using full words. When color is enabled, the first letter of each word
> is changed to a highlight color to signal that the first letter could be
> used as a command. Without color, brackets ("[]") are used around these
> first letters.
>
> This behavior was not previously tested directly in t3701, so add a test
> for it now. Since we use 'git add -i >actual <input' without
> 'force_color', the color system recognizes that colors are not available
> on stdout and will be disabled by default.
>
> This test would reproduce correctly with or without the fix in the
> previous commit to make sure that color.ui is respected in 'git add'.
>
> Reported-by: Phillip Wood <phillip.wood@dunelm.org.uk>
> Signed-off-by: Derrick Stolee <derrickstolee@github.com>
> ---
Thanks for adding this, the patch looks good. Strictly speaking you
don't need the "g" at the end of the sed expression as it only ever
matches a single instance within each line but that's not worth worrying
about.
Best Wishes
Phillip
> Here is the patch to add this test on top of the previous change.
>
> I've only validated this on my local computer, not through the
> GitGitGadget PR. If needed, I could send a v3 via GitGitGadget,
> but thought this would be a simple-enough addition here.
>
> Thanks,
> -Stolee
>
> t/t3701-add-interactive.sh | 23 +++++++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/t/t3701-add-interactive.sh b/t/t3701-add-interactive.sh
> index a93fe54e2ad..df3e85fc8d6 100755
> --- a/t/t3701-add-interactive.sh
> +++ b/t/t3701-add-interactive.sh
> @@ -734,6 +734,29 @@ test_expect_success 'colors can be overridden' '
> test_cmp expect actual
> '
>
> +test_expect_success 'brackets appear without color' '
> + git reset --hard &&
> + test_when_finished "git rm -f bracket-test" &&
> + test_write_lines context old more-context >bracket-test &&
> + git add bracket-test &&
> + test_write_lines context new more-context another-one >bracket-test &&
> +
> + test_write_lines quit >input &&
> + git add -i >actual <input &&
> +
> + sed "s/^|//g" >expect <<-\EOF &&
> + | staged unstaged path
> + | 1: +3/-0 +2/-1 bracket-test
> + |
> + |*** Commands ***
> + | 1: [s]tatus 2: [u]pdate 3: [r]evert 4: [a]dd untracked
> + | 5: [p]atch 6: [d]iff 7: [q]uit 8: [h]elp
> + |What now> Bye.
> + EOF
> +
> + test_cmp expect actual
> +'
> +
> test_expect_success 'colors can be skipped with color.ui=false' '
> git reset --hard &&
> test_when_finished "git rm -f color-test" &&
next prev parent reply other threads:[~2023-06-07 15:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 19:42 [PATCH] add: check color.ui for interactive add Derrick Stolee via GitGitGadget
2023-06-06 1:01 ` Junio C Hamano
2023-06-06 1:05 ` Junio C Hamano
2023-06-06 2:13 ` Jeff King
2023-06-06 13:32 ` Derrick Stolee
2023-06-06 14:20 ` [PATCH v2] " Derrick Stolee via GitGitGadget
2023-06-07 11:09 ` Phillip Wood
2023-06-07 13:33 ` Derrick Stolee
2023-06-12 17:09 ` Junio C Hamano
2023-06-07 13:44 ` [Patch v2 2/2] add: test use of brackets when color is disabled Derrick Stolee
2023-06-07 15:31 ` Phillip Wood [this message]
2023-06-12 17:13 ` Junio C Hamano
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=2143c98e-238b-8edc-a16c-be448a8b56e8@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=derrickstolee@github.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=peff@peff.net \
--cc=phillip.wood@dunelm.org.uk \
/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).