On Tue, Jul 07, 2020 at 10:58:48PM -0600, Grant Taylor wrote > 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.
Once you know what questions to ask, things become easier. Knowing that it was a TERM mismatch, a bit of googling turned up the "toe" command, which lists what your terminal supports. It looks like the install CD defaults to TERM="linux", which xterm (the app) doesn't support, according to "toe". Setting TERM on both ends to "xterm" solves the problem. -- Walter Dnes <[email protected]> I don't run "desktop environments"; I run useful applications
