Re: mail_check_recent does not work with homespool
* Michael Elkins on Friday, September 17, 2010 at 06:52:55 -0700
> On Fri, Sep 17, 2010 at 02:01:17PM +0200, Christian Ebert wrote:
>> $ mutt -Q spoolfile mbox_type
>> spoolfile="~/Maildir"
>> mbox_type=Maildir
>> $ stat ~/Maildir/new
>> 234881026 1168278 drwx------ 2 chris chris 0 68 "Sep 17 12:02:50 2010" "Sep
>> 17 01:41:20 2010" "Sep 17 01:41:20 2010" "Nov 17 13:45:43 2008" 4096 0 0
>> /Users/chris/Maildir/new
>>
>> Copy new message to homespool. Then:
>>
>> stat ~/Maildir/new
>> 234881026 1168278 drwx------ 3 chris chris 0 102 "Sep 17 12:02:50 2010" "Sep
>> 17 13:52:08 2010" "Sep 17 13:52:08 2010" "Nov 17 13:45:43 2008" 4096 0 0
>> /Users/chris/Maildir/new
>
> Can you please tell me which order those dates are (atime, ctime, mtime)?
atime, mtime, ctime
$ stat -s ~/Maildir/new | cut -d ' ' -f 10
st_mtime=1284732901
New message in ~/Maildir:
st_mtime=1284733668
> Do you have your spoolfile explicitly listed in your "mailboxes"
> command in your muttrc?
Yes, I have:
mailboxes "!"
(also, it worked before $mail_check_recent was introduced)
I just tried without it, and it does not influence the behaviour.
> The new mail detection doesn't depend on pathnames, so the fact that
> it works on other Maildir format mailboxes is perplexing.
Does it work without --with-homespool?
c
--
_BAUSTELLEN_ lesen! --->> http://www.blacktrash.org/baustellen