Re: [gentoo-user] vim-in-pine problem

[Jorge Almeida <jalmeida@math.ist.utl.pt>]

On Fri, 20 Oct 2006, Willie Wong wrote:
>>
>> Is there something I can do to try to find the culprit? (Using pico is a
>> real pain, I'm already tired after writing this message!)
>
> Do you have physical access to the remote machine? If you do, try and
> see if you can reproduce it locally at the remote machine, just to
Not until monday. But I sent mail yesterday at that box, and didn't
notice anything wrong.
> rule out ssh being the culprit. (Or perhaps you can try running pine
> in a screen session. If ssh is alive, and vim is AWOL, you should be
> able to C-a C-d and detach the screen session.)
I tried but the problem didn't manifest. Neither did it without screen
(it doesn't manifest always), so it's not conclusive...
>
> Did you upgrade vim? or Pine? What versions of those are you running?
I emerge sync and emerge -NDu world almost every day, so the versions are
the last stable ones (pine-4.64-r3 and vim-7.0.17). There was no upgrade
of either package in the last week...
>
> If you suspect the kernel is the problem, is there anything in the
> logs? (dmesg or otherwise).
I really can't imagine why the kernel would affect only the combination
ssh+pine+vim, but on the other hand there aren't many suspects!
Nothing in dmesg/logs...

My ISP is really crappy and the connection was not at its best, but, as
I said, other ssh sessions continued alive and responding well (I could
see the output of "ls" immediately, whereas I couldn't change mode, or
move arrows, in vim-in-pine. Note that I could use vim in other ssh
sessions, just not on pine!
>
Thanks.

-- 
Jorge Almeida
-- 
gentoo-user@gentoo.org mailing list