On 20:36 02 Mar 2002, christophe barbé <[EMAIL PROTECTED]> wrote: | > For myself, I don't keep mutt up all the time - I open it to read | > email and quit when done. So I'm not using mutt's "new mail" monitor. | > Also, I'm not using the shell's $MAIL monitor (which depends on atime, | > pronouncing new email with atime($MAIL) < mtime($MAIL)). | > Instead, I have my procmail recipe write a line to a log file when | > interesting email arrives (i.e. only when one of a few recipes fires). | > And I have a small window which tails that logfile. [...] | | Thank you for you answer, happy to not be alone ;-). | For my main inbox I have my gkrellm Mailwatch Plugin that keep track of | new mail without atime. | My problem is with mailing lists. As I understand it (but I haven't tried it, | if I quit mutt after reading and relaunch each later (which is not a big | overhead) mutt will reports new mails in mailing-list boxes even if I | have already read all mails.
Shouldn't. Except for MH folders, mutt keeps message status in a header, and so will recognise new messages reliably because they will either lack the header line altogether or have the header line with an "N" flag. | I was thinking about an mutt option to detect new mails without | depending on atime (something like keeping an internal atime and | checking mbox content when mtime > internal atime). If you keep it open all the time it may work, provided you only ever have the folder open in one mutt at a time (which I suppose is desirable anyway - I enforce that in my wrapper script). However, I think you'll find it unnecessary. -- Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/ What's a pencil? Is that like a PDA stylus? - [EMAIL PROTECTED] (Elizabeth Schwartz)
