On Thu, Sep 06, 2001 at 02:16:07PM -0400, Derek Martin wrote:
> On Thu, Sep 06, 2001 at 07:51:41AM -0400, Brendan Cully wrote:
> > First of all, for anything IMAP-related I'd strongly recommend you pick
> > up the latest mutt beta (currently 1.3.22.1), since that code has
> > changed quite a lot.
On Thu, Sep 06, 2001 at 12:51:56AM -0400, Derek Martin wrote:
> On some systems where I run mutt, it works as you would expect. On
> others, after I read all the new messages in a folder which it marked
> as having new mail, and then try to change to the next folder with new
> mail, but it would
On Thu, Sep 06, 2001 at 11:07:41AM +0200, Thomas Roessler wrote:
> On 2001-09-06 00:51:56 -0400, Derek Martin wrote:
>
> >On some systems where I run mutt, it works as you would expect.
> >On others, after I read all the new messages in a folder which it
> >marked as having new mail, and then t
On Thursday, 06 September 2001 at 00:51, Derek Martin wrote:
> Hey all,
>
> I'm using mutt 1.2.5i, and I've got a very strange problem with new
> mail. I'm using mutt to access IMAP folders, and the binary and
> shared data reside on NFS. Here's the problem:
>
> On some systems where I run mut
On 2001-09-06 00:51:56 -0400, Derek Martin wrote:
>On some systems where I run mutt, it works as you would expect.
>On others, after I read all the new messages in a folder which it
>marked as having new mail, and then try to change to the next
>folder with new mail, but it would send me back
Hey all,
I'm using mutt 1.2.5i, and I've got a very strange problem with new
mail. I'm using mutt to access IMAP folders, and the binary and
shared data reside on NFS. Here's the problem:
On some systems where I run mutt, it works as you would expect. On
others, after I read all the new messa
