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 1GaytS-0001H2-3G for garchives@archives.gentoo.org; Fri, 20 Oct 2006 18:14:54 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k9KICn09025012; Fri, 20 Oct 2006 18:12:49 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 k9KI9H25029074 for ; Fri, 20 Oct 2006 18:09:17 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 k9KI9HDe022669 for ; Fri, 20 Oct 2006 19:09:17 +0100 Received: (qmail 14874 invoked from network); 20 Oct 2006 19:09:16 +0100 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 20 Oct 2006 19:09:16 +0100 Date: Fri, 20 Oct 2006 19:09:16 +0100 (WEST) From: Jorge Almeida To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] vim-in-pine problem Message-ID: 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: a73dfc23-d378-4ee8-92e6-c22e11c38fd9 X-Archives-Hash: a186b5c9ba5715bc937b79af588e0398 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!) -- Jorge Almeida -- gentoo-user@gentoo.org mailing list