Re: Mutt, unnoticed new mail and improper access/change times

2001-01-25 Thread David Wright
Quoting Carel Fellinger ([EMAIL PROTECTED]): Yep, that seems to be the tradition in Open Software Circles anyway, so be my guest:) I improved a bit on that recepy (better locking): | cat $FOLDER touch -m -d next sec $FOLDER Thanks - I've had to modify it slightly for a Sun because

Re: Mutt, unnoticed new mail and improper access/change times

2001-01-25 Thread Carel Fellinger
On Thu, Jan 25, 2001 at 03:42:47PM +, David Wright wrote: ... Thanks - I've had to modify it slightly for a Sun because touch isn't so clever, and it becomes either cat $BOX sleep 2 touch -m $BOX or, better locking but much worse looking, cat $BOX env TZ=EST touch -m -t `date

Re: Mutt, unnoticed new mail and improper access/change times

2001-01-25 Thread David Wright
Quoting Carel Fellinger ([EMAIL PROTECTED]): On Thu, Jan 25, 2001 at 03:42:47PM +, David Wright wrote:... Thanks - I've had to modify it slightly for a Sun because touch isn't so clever, and it becomes either wonder what happens of you go to far west and hit the date border:) Yes,

Mutt, unnoticed new mail and improper access/change times

2001-01-22 Thread Carel Fellinger
Hai, lately I've problems with mutt detecting the arrival of new mail. I use procmail to sort my mail in folders, for each list a seperate folder. In order to weed out the empty mailboxes in the c tab-tab window, I've unset save_empty and now mutt doesn't seem to notice the first arrived mail.

Re: Mutt, unnoticed new mail and improper access/change times

2001-01-22 Thread David Wright
Quoting Carel Fellinger ([EMAIL PROTECTED]): In order to weed out the empty mailboxes in the c tab-tab window, I've unset save_empty ... presumably so it deletes empty mailboxes. It seems to have to do with access and modification times, the first mail to be delivered to a non-existing

Re: Mutt, unnoticed new mail and improper access/change times

2001-01-22 Thread Carel Fellinger
On Mon, Jan 22, 2001 at 07:17:08PM +, David Wright wrote: ... Nice. The problem hadn't worried me enough to look for a workaround, but may I steal that? Yep, that seems to be the tradition in Open Software Circles anyway, so be my guest:) I improved a bit on that recepy (better locking):