From 217e06641d6cc9239d1017c2ccc7d1e67d7c286d Mon Sep 17 00:00:00 2001 From: djcb Date: Wed, 23 Nov 2016 23:26:12 +0200 Subject: [PATCH] mu4e: minor cleanup in docstrings --- mu4e/mu4e-vars.el | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/mu4e/mu4e-vars.el b/mu4e/mu4e-vars.el index c2463f6a..c80426b9 100644 --- a/mu4e/mu4e-vars.el +++ b/mu4e/mu4e-vars.el @@ -91,24 +91,20 @@ background." :safe 'booleanp) (defcustom mu4e-index-cleanup t - "Whether to run a cleanup face after indexing -- that is, see + "Whether to run a cleanup phase after indexing -- that is, see if the is a message in the filesystem for each file in the message store. Having this option as `t' ensures that no non-existing mesages are shown but can also be quite slow with -large message stores." - :type 'boolean - :group 'mu4e - :safe 'booleanp) +large message stores." :type 'boolean :group 'mu4e :safe +'booleanp) (defcustom mu4e-index-lazy-check nil - "Whether to run do a 'lazy check' for deciding whether to -indexing a message. When this is set to `t', mu only uses the -directory timestamps to decide on whether it needs to check the -messages beneath it, which would miss messages that are modified -outside mu. On the other hand, it's significantly faster." - :type 'boolean - :group 'mu4e - :safe 'booleanp) + "Whether to only use a 'lazy check' to decide whether a message +needs (re)indexing or not. When this is set to `t', mu only uses +the directory timestamps to decide on whether it needs to check +the messages beneath it, which would miss messages that are +modified outside mu. On the other hand, it's significantly +faster." :type 'boolean :group 'mu4e :safe 'booleanp) (defcustom mu4e-update-interval nil