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 1Gb00t-0001Kn-Je for garchives@archives.gentoo.org; Fri, 20 Oct 2006 19:26:40 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k9KJNHvB023478; Fri, 20 Oct 2006 19:23:17 GMT Received: from Princeton.EDU (postoffice02.Princeton.EDU [128.112.130.38]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k9KJKVkk008870 for ; Fri, 20 Oct 2006 19:20:31 GMT Received: from smtpserver1.Princeton.EDU (smtpserver1.Princeton.EDU [128.112.129.65]) by Princeton.EDU (8.13.8/8.13.8) with ESMTP id k9KJKUQf002973 for ; Fri, 20 Oct 2006 15:20:30 -0400 (EDT) Received: from sep.dynalias.net (fez.Princeton.EDU [128.112.129.190]) (authenticated bits=0) by smtpserver1.Princeton.EDU (8.12.9/8.12.9) with ESMTP id k9KJKTZI017592 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT) for ; Fri, 20 Oct 2006 15:20:30 -0400 (EDT) Received: by sep.dynalias.net (Postfix, from userid 1001) id E45B218B99B; Fri, 20 Oct 2006 15:22:33 -0400 (EDT) Date: Fri, 20 Oct 2006 15:22:33 -0400 From: Willie Wong To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] vim-in-pine problem Message-ID: <20061020192233.GA12932@princeton.edu> Mail-Followup-To: gentoo-user@lists.gentoo.org References: 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 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Archives-Salt: 515eecb4-1178-4465-ac04-e2150066326e X-Archives-Hash: b88417bbbbc9a55697d18a56e1423d11 On Fri, Oct 20, 2006 at 07:09:16PM +0100, Penguin Lover Jorge Almeida squawked: > I'm having a problem when composing mail in a ssh session since I > upgraded the remote kernel to 2.6.17-gentoo-r8 (I had 2.6.17-gentoo-r7 > before). I'm using vim to compose a message in pine and suddenly it stops > responding (nothing happens, whatever key I press). I have to kill the > session (by killing the window). On the other hand, if I use the embedded > pico to compose, there's no problem. Moreover, I had several ssh sessions > active, and they responded as usual, so it's not as the connection went > down... > > I always compose messages this way and never had this kind of problem. It > happened twice since yesterday, when I upgraded the kernel (can figure out > what else can be...). The local kernel is the same (and it was upgraded > some time ago). > > 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 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.) Did you upgrade vim? or Pine? What versions of those are you running? If you suspect the kernel is the problem, is there anything in the logs? (dmesg or otherwise). W -- I found my "inner child" ... and put the brat up for adoption. Sortir en Pantoufles: up 56 days, 12:48 -- gentoo-user@gentoo.org mailing list