| 1 |
John Jolet wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> On Jan 23, 2006, at 2:41 PM, Tom Smith wrote: |
| 5 |
> |
| 6 |
>> John Jolet wrote: |
| 7 |
>> |
| 8 |
>>> |
| 9 |
>>> On Jan 23, 2006, at 1:56 PM, Tom Smith wrote: |
| 10 |
>>> |
| 11 |
>>>> John Jolet wrote: |
| 12 |
>>>> |
| 13 |
>>>>> |
| 14 |
>>>>> On Jan 23, 2006, at 1:00 PM, Tom Smith wrote: |
| 15 |
>>>>> |
| 16 |
>>>>>> John Jolet wrote: |
| 17 |
>>>>>> |
| 18 |
>>>>>>> what is the output of "echo $TERM"? |
| 19 |
>>>>>> |
| 20 |
>>>>>> |
| 21 |
>>>>>> |
| 22 |
>>>>>> |
| 23 |
>>>>>> pcadobe ~ # echo $TERM |
| 24 |
>>>>>> linux |
| 25 |
>>>>>> pcadobe ~ # |
| 26 |
>>>>>> |
| 27 |
>>>>> try "export TERM=vt220" and see if that helps. |
| 28 |
>>>> |
| 29 |
>>>> |
| 30 |
>>>> |
| 31 |
>>>> This did work for "pstree" but seriously broke functionality in |
| 32 |
>>>> Vim, an |
| 33 |
>>>> app that is heavily used via SSH. |
| 34 |
>>>> |
| 35 |
>>>> I did notice something interesting, though. If I set (in Kermit) |
| 36 |
>>>> |
| 37 |
>>>> Terminal Type: vt220 |
| 38 |
>>>> Terminal Remote-Charset: cp437 |
| 39 |
>>>> |
| 40 |
>>> the next thing I would try is export the TERM value at the gentoo |
| 41 |
>>> command-line and the TERM value at the other end both vt220. |
| 42 |
>>> |
| 43 |
>>> Okay, now for another question, that may or may not be relevant. why |
| 44 |
>>> is kermit involved? if you are sshing into another box, why use |
| 45 |
>>> kermit? |
| 46 |
>> |
| 47 |
>> |
| 48 |
>> Sorry, I probably should've clarified this from the beginning... |
| 49 |
>> |
| 50 |
>> I'm using Kermit 95 on Windows XP Pro to connect to my Linux server. |
| 51 |
>> (Kermit 95 is a commercial, Windows-only product; while ckermit is the |
| 52 |
>> *nix version and freely available.) That said... |
| 53 |
>> |
| 54 |
>> I believe I've done the equivalent of what you're asking. I ran the |
| 55 |
>> "export TERM=vt220" within the SSH session (on the server) and then |
| 56 |
>> changed Kermit 95 to match that terminal type. (This should have the |
| 57 |
>> same effect as what you suggested, right?) |
| 58 |
>> |
| 59 |
> if this were a unix-unix connection, yes. have you tried PutTTY? |
| 60 |
> free windows ssh client. VERY nice. (not trying to bash kermit 95, |
| 61 |
> but haven't used it since...well 95) |
| 62 |
|
| 63 |
(Sorry if this is a duplicate post... I posted my previous response with |
| 64 |
the wrong email address and wasn't sure if it'd go through.) |
| 65 |
|
| 66 |
Yes, I used PuTTY back in the day. I came to like Kermit (I use it both |
| 67 |
in Windows and Linux) because of some of it's advanced features like |
| 68 |
scripting. Kermit hasn't been updated much over the last... Hm, I don't |
| 69 |
know the last time it was updates. :-| Anyway, I think they're both good |
| 70 |
clients, Kermit just supports a LOT of features that I find useful that |
| 71 |
PuTTY doesn't (yet?) support. |
| 72 |
|
| 73 |
Did you (or anyone else :-) ) have any other suggestions to this dilemma? |
| 74 |
-- |
| 75 |
gentoo-user@g.o mailing list |
Archives