public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jorge Almeida <jalmeida@math.ist.utl.pt>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] vim-in-pine problem
Date: Fri, 20 Oct 2006 19:09:16 +0100 (WEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610201854510.14863@jmaa.math.ist.utl.pt> (raw)

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



             reply	other threads:[~2006-10-20 18:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 18:09 Jorge Almeida [this message]
2006-10-20 19:22 ` [gentoo-user] vim-in-pine problem Willie Wong
2006-10-20 23:21   ` Jorge Almeida
2006-10-21  3:40     ` Willie Wong
2006-10-21  7:35       ` Jorge Almeida
2006-10-21  4:28 ` Philip Webb
2006-10-21  7:45   ` Jorge Almeida
2006-10-21  8:05     ` Philip Webb
2006-10-21  8:50       ` Jorge Almeida
2006-10-24  3:11         ` Bryan Whitehead

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0610201854510.14863@jmaa.math.ist.utl.pt \
    --to=jalmeida@math.ist.utl.pt \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox