| 1 |
On 8/7/20 12:58 pm, 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 |
| 12 |
> to something MASSIVELY wrong for your actual terminal. I.e. trying to |
| 13 |
> send fancy xterm / ANSI control sequences to an old dumb terminal like |
| 14 |
> a VT100. |
| 15 |
> |
| 16 |
> Seeing as how ANSI / XTERM* is effectively a significant super set of |
| 17 |
> VT100, setting the TERM variable to an older less capable value does |
| 18 |
> little other than limit features. |
| 19 |
> |
| 20 |
> That being said, I have seen problems when there is a size mismatch |
| 21 |
> between what's running on the host and the terminal. Sort of like if |
| 22 |
> you re-sized the window after starting nano (et al.). Things can get |
| 23 |
> weird then. |
| 24 |
> |
| 25 |
> Beyond any of this, I'd be quite curious what problems you're having. |
| 26 |
> |
| 27 |
Try hitting the F11 key (full screen, hit again to go back )when logged |
| 28 |
in to rewrite the screen with the session rereading the screen sizes. |
| 29 |
|
| 30 |
BillK |
Archives