From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] SSH xterm not working properly during install
Date: Tue, 7 Jul 2020 22:58:48 -0600 [thread overview]
Message-ID: <2c6a0945-60d3-4728-d814-9c684d84fc6b@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20200708044003.GA30312@waltdnes.org>
On 7/7/20 10:40 PM, Walter Dnes wrote:
> Thanks, I missed that. I'll try again and see how it goes.
If you continue to have problems, I would very much like to know the
particulars.
My experience has been that changing the TERM environment variable has
had very little success in fixing things like this.
In fact, the only way that I see it working is if you are TERM is set to
something MASSIVELY wrong for your actual terminal. I.e. trying to send
fancy xterm / ANSI control sequences to an old dumb terminal like a VT100.
Seeing as how ANSI / XTERM* is effectively a significant super set of
VT100, setting the TERM variable to an older less capable value does
little other than limit features.
That being said, I have seen problems when there is a size mismatch
between what's running on the host and the terminal. Sort of like if
you re-sized the window after starting nano (et al.). Things can get
weird then.
Beyond any of this, I'd be quite curious what problems you're having.
--
Grant. . . .
unix || die
next prev parent reply other threads:[~2020-07-08 4:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 2:02 [gentoo-user] SSH xterm not working properly during install Walter Dnes
2020-07-08 4:06 ` tastytea
2020-07-08 4:40 ` Walter Dnes
2020-07-08 4:58 ` Grant Taylor [this message]
2020-07-08 7:46 ` William Kenworthy
2020-07-08 19:35 ` [gentoo-user] [SOLVED] " Walter Dnes
2020-07-08 13:48 ` [gentoo-user] " Grant Edwards
2020-07-08 19:42 ` [gentoo-user] [SOLVED] " Walter Dnes
2020-07-09 6:20 ` Walter Dnes
2020-07-09 2:05 ` [gentoo-user] " james
2020-07-09 2:41 ` james
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=2c6a0945-60d3-4728-d814-9c684d84fc6b@spamtrap.tnetconsulting.net \
--to=gtaylor@gentoo.tnetconsulting.net \
--cc=gentoo-user@lists.gentoo.org \
/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