This might be on the way to tracking this down.
New mail arrived while sending mail (between hitting "y" and regaining
control of mutt). Mutt didn't catch new mail arriving, and couldn't be
motivated to check the mailbox until more new mail arrived.
Ben
On Mon, May 01, 2000 at 05:55:57PM -0500
On Tue, May 02, 2000 at 12:36:46PM -0500, David DeSimone wrote:
> Mikko Hänninen <[EMAIL PROTECTED]> wrote:
> >
> > I use Maildir over NFS. I find myself frequently in a situation where
> > I see in my incoming mail log that I've gotten mail in a particular
> > folder while I'm reading it, but Mu
Mikko Hänninen <[EMAIL PROTECTED]> wrote:
>
> I use Maildir over NFS. I find myself frequently in a situation where
> I see in my incoming mail log that I've gotten mail in a particular
> folder while I'm reading it, but Mutt doesn't seem to notice it. It
> certainly takes much longer than the 5
David DeSimone <[EMAIL PROTECTED]> wrote on Mon, 01 May 2000:
> Anyway, Mutt is supposed to notice new mail without being told to look
> for it.
I have $mail_check set to 5 (and $timeout at 600, but I don't think
that matters). I use Maildir over NFS. I find myself frequently in a
situation whe
Benjamin Korvemaker <[EMAIL PROTECTED]> wrote:
>
> Can I force mutt to rescan the current folder (I'm using maildirs)? $
> only commits the changes, but doesn't pick up the new mail in the box,
> yet gbuffy lets me know there's more mail.
There isn't a function to cause a re-scan, because Mutt i
I've probably just overlooked it, although I've looked a few times (when
agravation exceeded laziness) and can't find it in the online help or user
manual.
Can I force mutt to rescan the current folder (I'm using maildirs)? $ only
commits the changes, but doesn't pick up the new mail in the box,
