From: Junio C Hamano <gitster@pobox.com>
To: Jeffrey Walton <noloader@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: WARNING: terminal is not fully functional
Date: Thu, 27 Jan 2022 10:44:18 -0800 [thread overview]
Message-ID: <xmqqczkd2f3x.fsf@gitster.g> (raw)
In-Reply-To: <CAH8yC8k53a4xcDh34XqoA0VCcxG+Y+mE-rb1MKMd_Z+r-t=_Bw@mail.gmail.com> (Jeffrey Walton's message of "Thu, 27 Jan 2022 02:05:18 -0500")
Jeffrey Walton <noloader@gmail.com> writes:
> On Thu, Jan 27, 2022 at 1:15 AM Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Jeffrey Walton <noloader@gmail.com> writes:
>>
>> > I needed to install Git on Ubuntu 8. Git seems to work Ok for most
>> > task, but this is unusual:
>> >
>> > $ git diff
>> > WARNING: terminal is not fully functional
>> > - (press RETURN)
>> >
>> > Here's the terminal:
>> >
>> > $ echo $TERM
>> > xterm-256color
>> ...
>> Something to try quickly would be:
>>
>> $ export TERM=vt100; less README.md
>>
>> As the termcap/terminfo entry for vt100 is usually more widely
>> available, this may unblock you.
>>
>> > It seems like loss of colors on an old platform is not that important.
>> > However, the message being printed creates an actionable item that
>> > needs attention. I think no message would be a better option.
>>
>> You would want to redirect it to folks who work on "less" ;-)
>
> Oh, sorry about that.
No need to be sorry for that.
I seem to have these terminfo database entries for terminals whose
name begin with 'x':
$ /bin/ls /lib/terminfo/x
xterm
xterm-256color
xterm-color
xterm-debian
xterm-mono
xterm-r5
xterm-r6
xterm-vt220
xterm-xfree86
my suspicion is that you are lacking xterm-256color for some reason.
These usually come from ncurses-base package if I am not mistaken.
prev parent reply other threads:[~2022-01-27 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 6:00 WARNING: terminal is not fully functional Jeffrey Walton
2022-01-27 6:15 ` Junio C Hamano
2022-01-27 7:05 ` Jeffrey Walton
2022-01-27 18:44 ` Junio C Hamano [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=xmqqczkd2f3x.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=noloader@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.