Improve documentation on quick syncs
Make clear that quick syncs do not happen inbetween full syncs (ie they are part of the regular autorefresh intervals and don't happen within them). This part of the documentation had confused many. Signed-off-by: dtk <d.t.k@gmx.de> Modified-by: Sebastian Spaeth <Sebastian@SSpaeth.de> Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
This commit is contained in:
parent
9e734006f6
commit
38dfa1d684
@ -171,13 +171,17 @@ remoterepository = RemoteExample
|
||||
|
||||
# autorefresh = 5
|
||||
|
||||
# You can tell offlineimap to do a number of quicker synchronizations
|
||||
# between full updates. A quick synchronization only synchronizes
|
||||
# if a Maildir folder has changed, or if an IMAP folder has received
|
||||
# new messages or had messages deleted. It does not update if the
|
||||
# only changes were to IMAP flags. Specify 0 to never do quick updates,
|
||||
# -1 to always do quick updates, or a positive integer to do that many
|
||||
# quick updates between each full synchronization (requires autorefresh).
|
||||
# OfflineImap can replace a number of full updates by quick
|
||||
# synchronizations. It only synchronizes a folder if 1) a Maildir
|
||||
# folder has changed, or 2) if an IMAP folder has received new messages
|
||||
# or had messages deleted, ie it does not update if only IMAP flags have
|
||||
# changed. Full updates need to fetch ALL flags for all messages, so
|
||||
# this makes quite a performance difference (especially if syncing
|
||||
# between two IMAP servers).
|
||||
# Specify 0 for never, -1 for always (works even in non-autorefresh
|
||||
# mode), or a positive integer <n> to do <n> quick updates before doing
|
||||
# another full synchronization (requires autorefresh). Updates are
|
||||
# always performed after <autorefresh> minutes, be they quick or full.
|
||||
|
||||
# quick = 10
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user