<p>It seems this was the behavior I saw too, which I thought was a bug for the same reason. I suggest filing a documentation bug report.</p>
<div class="gmail_quote">On Apr 11, 2011 6:55 PM, "dtk" <<a href="mailto:d.t.k@gmx.de">d.t.k@gmx.de</a>> wrote:<br type="attribution">> Excerpts from Sebastian Spaeth's message of Mon Apr 11 18:41:51 +0200 2011:<br>
>> On Mon, 11 Apr 2011 10:33:21 +0200, dtk <<a href="mailto:d.t.k@gmx.de">d.t.k@gmx.de</a>> wrote:<br>>><br>>> > 'daemon mode'[0] right now, but quick syncs don't work.<br>>> > in my config, and the autorefresh setting works as expected, the IMAP server<br>
>> > being checked for new mail every 300 seconds. But if I receive new mail in<br>>> > between, it isn't detected until the next 'major' check.<br>>><br>>> That is bad.<br>> indeed ;)<br>
> <br>>> I certainly get new mail with it (not daemon mode<br>>> though).<br>> hmm, by daemon mode you too mean specifying autorefresh so offlineimap doesn't<br>> exit after the first sync? In that case I don't think I understand how<br>
> quicksyncs behave in your case.<br>> <br>>> I set my quick setting to -1 in .offlineimaprc..., I would<br>>> never get new mail otherwise.<br>> why is that? doesn't -1 make all syncs quick ones? k, maybe not if not in daemon<br>
> mode ;)<br>> <br>>> Is that IMAP<->IMAP? Or IMAP<->Maildir ?<br>> It's IMAP<->Maildir<br>> <br>>> We would need to debug offlineimap/folder/IMAP.py:quickchanged() which<br>>> determines whether to skip a check. There are currently no debug outputs<br>
>> in that function...<br>> k, actually I misread the documentation :/ I'm sorry :( I thought<br>> [quote]<br>> # You can tell offlineimap to do a number of quicker synchronizations<br>> # between full updates.<br>
> [/quote]<br>> meant actually *between* full syncs, where when full syncs would take place was<br>> configured via autorefresh. I expected configuring<br>> [config]<br>> autorefresh = 5<br>> quick = 10<br>
> [/config]<br>> would full sync to take place every 5 * 60 = 300 seconds, with quick syncs being<br>> triggered every 300 / 10 = 30 seconds. Stupid me *duh*<br>> <br>> Only when debugging sync() (thanks for the hint, Sebastian), I realized that<br>
> quick specifies how many quick syncs are performed before another full sync is<br>> done, syncs independent of type still _only_ being done every <autorefresh><br>> minutes.<br>> <br>> So<br>> [config]<br>
> autorefresh = 0.5<br>> quick = 10<br>> [/config]<br>> nets me 1 full sync, 10 quick syncs after 30 seconds each, before after 5.5<br>> minutes another full sync is performed. FTR -.-<br>> <br>> sorry for the false alarm :/<br>
> dtk<br>> <br>> _______________________________________________<br>> OfflineIMAP-project mailing list<br>> <a href="mailto:OfflineIMAP-project@lists.alioth.debian.org">OfflineIMAP-project@lists.alioth.debian.org</a><br>
> <a href="http://lists.alioth.debian.org/mailman/listinfo/offlineimap-project">http://lists.alioth.debian.org/mailman/listinfo/offlineimap-project</a><br>> <br>> OfflineIMAP homepage: <a href="http://software.complete.org/offlineimap">http://software.complete.org/offlineimap</a><br>
</div>