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: Re: [gentoo-user] vim-in-pine problem
Date: Sat, 21 Oct 2006 08:35:26 +0100 (WEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610210831001.18835@jmaa.math.ist.utl.pt> (raw)
In-Reply-To: <20061021034028.GD24986@princeton.edu>

On Fri, 20 Oct 2006, Willie Wong wrote:

> On Sat, Oct 21, 2006 at 12:21:47AM +0100, Penguin Lover Jorge Almeida squawked:
>> I tried but the problem didn't manifest. Neither did it without screen
>> (it doesn't manifest always), so it's not conclusive...
>
> My suspicion is still on ssh over a flaky connection.
>
> With only two incidents, I don't really see any way of pinpointing the
> program at fault. For all we know it could be a problem with vim,
> period, not even involving pine. Or it could be a problem with pine,
> regarless of which editor you use.
>
> In any case, if the problem is transcient and not-reproducible, I
> think you can stop worring about it. But if you know that your ISP is
Yes, I'll wait and see...
> horrible, I would really suggest doing all work in a screen session
> when working on the remote machine.
Seems a good idea, at least to preserve half-done work...
>
> HTH.
>
Cheers.
-- 
Jorge Almeida
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-10-21  7:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 18:09 [gentoo-user] vim-in-pine problem Jorge Almeida
2006-10-20 19:22 ` Willie Wong
2006-10-20 23:21   ` Jorge Almeida
2006-10-21  3:40     ` Willie Wong
2006-10-21  7:35       ` Jorge Almeida [this message]
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.0610210831001.18835@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