| 1 |
On 7/7/20 10:40 PM, Walter Dnes wrote: |
| 2 |
> Thanks, I missed that. I'll try again and see how it goes. |
| 3 |
|
| 4 |
If you continue to have problems, I would very much like to know the |
| 5 |
particulars. |
| 6 |
|
| 7 |
My experience has been that changing the TERM environment variable has |
| 8 |
had very little success in fixing things like this. |
| 9 |
|
| 10 |
In fact, the only way that I see it working is if you are TERM is set to |
| 11 |
something MASSIVELY wrong for your actual terminal. I.e. trying to send |
| 12 |
fancy xterm / ANSI control sequences to an old dumb terminal like a VT100. |
| 13 |
|
| 14 |
Seeing as how ANSI / XTERM* is effectively a significant super set of |
| 15 |
VT100, setting the TERM variable to an older less capable value does |
| 16 |
little other than limit features. |
| 17 |
|
| 18 |
That being said, I have seen problems when there is a size mismatch |
| 19 |
between what's running on the host and the terminal. Sort of like if |
| 20 |
you re-sized the window after starting nano (et al.). Things can get |
| 21 |
weird then. |
| 22 |
|
| 23 |
Beyond any of this, I'd be quite curious what problems you're having. |
| 24 |
|
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Grant. . . . |
| 29 |
unix || die |
Archives