From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Gb3kW-0002NM-Ks for garchives@archives.gentoo.org; Fri, 20 Oct 2006 23:26:01 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k9KNNw2S016859; Fri, 20 Oct 2006 23:23:58 GMT Received: from cubo.math.ist.utl.pt (cubo.math.ist.utl.pt [193.136.196.1]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k9KNLoLW025986 for ; Fri, 20 Oct 2006 23:21:50 GMT Received: from jmaa.math.ist.utl.pt (jmaa.math.ist.utl.pt [193.136.196.112]) by cubo.math.ist.utl.pt (8.13.7/8.13.6) with ESMTP id k9KNLnvg014353 for ; Sat, 21 Oct 2006 00:21:50 +0100 Received: (qmail 15388 invoked from network); 21 Oct 2006 00:21:47 +0100 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 21 Oct 2006 00:21:47 +0100 Date: Sat, 21 Oct 2006 00:21:47 +0100 (WEST) From: Jorge Almeida To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] vim-in-pine problem In-Reply-To: <20061020192233.GA12932@princeton.edu> Message-ID: References: <20061020192233.GA12932@princeton.edu> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archives-Salt: baa2f336-9b4e-4811-b690-01894bdcd220 X-Archives-Hash: 82cde8f98377b9fe5d6ff8fee99b640b 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