| 1 |
On Tue, Jul 07, 2020 at 10:58:48PM -0600, Grant Taylor wrote |
| 2 |
> On 7/7/20 10:40 PM, Walter Dnes wrote: |
| 3 |
> > Thanks, I missed that. I'll try again and see how it goes. |
| 4 |
> |
| 5 |
> If you continue to have problems, I would very much like to know the |
| 6 |
> particulars. |
| 7 |
> |
| 8 |
> My experience has been that changing the TERM environment variable has |
| 9 |
> had very little success in fixing things like this. |
| 10 |
> |
| 11 |
> In fact, the only way that I see it working is if you are TERM is set to |
| 12 |
> something MASSIVELY wrong for your actual terminal. I.e. trying to send |
| 13 |
> fancy xterm / ANSI control sequences to an old dumb terminal like a VT100. |
| 14 |
|
| 15 |
Once you know what questions to ask, things become easier. Knowing |
| 16 |
that it was a TERM mismatch, a bit of googling turned up the "toe" |
| 17 |
command, which lists what your terminal supports. It looks like the |
| 18 |
install CD defaults to TERM="linux", which xterm (the app) doesn't |
| 19 |
support, according to "toe". Setting TERM on both ends to "xterm" |
| 20 |
solves the problem. |
| 21 |
|
| 22 |
-- |
| 23 |
Walter Dnes <waltdnes@××××××××.org> |
| 24 |
I don't run "desktop environments"; I run useful applications |
Archives