Re: win-test: unknown terminal "xterm-256color", was Re: [RFC PATCH 6/6] ls-tree: introduce '--pattern' option
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Mar 28, 2023, 19:31 UTC
- Message-ID
- <xmqqbkkcfz9s.fsf@gitster.g>
- In-Reply-To
- <20230328180859.GB18558@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 12 quoted lines
> So it should be fine to just set TERM=dumb everywhere. What actually
> confuses me is that we try to do so already:
>
> $ git grep -B1 dumb ci/lib.sh
> ci/lib.sh-# GitHub Action doesn't set TERM, which is required by tput
> ci/lib.sh:export TERM=${TERM:-dumb}
>
> Pushing a stripped-down workflow file to just run "echo $TERM" shows
> that it seems to already be set by Actions to "dumb" on ubuntu-latest,
> but is xterm-256color on windows-latest.
>
> So maybe we just want to make the line above unconditionally set $TERM?I thought that Dscho earlier said xterm-256 is set by mingw when nothing is set to TERM, which explains why TERM=${TERM:-dumb} is not good enough to "fix" this one for them.
I am fine with an unconditional assignment for CI.
Thanks.