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: Wed, 26 Jan 2022 22:15:43 -0800 [thread overview]
Message-ID: <xmqqr18t4sc0.fsf@gitster.g> (raw)
In-Reply-To: <CAH8yC8kYP2Sth+vUZMzHujKQZC6r1kFf+Lz=6_WRs4GFR65B9g@mail.gmail.com> (Jeffrey Walton's message of "Thu, 27 Jan 2022 01:00:06 -0500")
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
A short answer. You are using "less" as the pager, but it is not
working with your terminal. Likely reason is perhaps you are
missing terminfo/termcap database entry for that terminal.
I have working xterm-256color, so
$ TERM=xterm-256color less README.md
works as expected, but using a (bogus) terminal that no system would
have ever heard of, e.g.
$ TERM=no-such-terminal-exists less README.md
results in exactly the symptom you are observing.
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" ;-)
next prev parent reply other threads:[~2022-01-27 6:16 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 [this message]
2022-01-27 7:05 ` Jeffrey Walton
2022-01-27 18:44 ` 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=xmqqr18t4sc0.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.