* mu4e.texi: some updates to the docs
* mu-find: add the summary-len option
* small cleanups (macos)
* update mu-index manpage (remove the outdate exit codes)
* mu4e: update the list of known mailing-lists
* better error message for some broken queries
* mu-date: small optimization
* update mu_date_str_to_time_t for macos

  at macos this function /seemed/ to massively leak, when looking at the
  valgrind output on macos (but not linux). with this update, this
  leak(?) is gone.
* fix the mu_util_fputs_encoded/bsd heisenbug

  it seems g_locale_from_utf8 behaves a bit differently on bsd/macosx,
  causing a segfault (but when run under gdb!). this code path was hit
  for messages with encoding problems in non-utf8 locales
* update gitignore
Remove explicit dependency on 'ido'

Now uses 'completing-read' rather than 'ido-completing-read' when
prompting for a maildir. This leaves the way open for the use of
alternative completing-read replacements, such as 'helm'
(https://github.com/emacs-helm/helm).

If the user still wants to use 'ido-completing-read' then they can do
this through 'ido-ubiquitous-mode'
(https://github.com/technomancy/ido-ubiquitous)
Add a customisation option for completion system

Introduced mu4e-use-native-completing-read customisation setting to
control which type of minibuffer completion system mu4e uses.

If unset (the default), then ido-completing-read is used, which provides
an intuitive completion system even if users don't customise mu4e
further.

If this is set to 't' then mu4e uses the standard Emacs completing-read
function for this. This can be chosen if the user prefers the native
method (perhaps unlikely), or else if they have another minibuffer
completion system that overrides completing-read and would prefer to use
that. An example of that is helm, which can override completing-read
if the helm-mode function is called.
New flexible method of customising completing-read

Added the customisation option 'mu4e-completing-read-function' which can
be used to choose which method of input-with-completion will be used by
mu4e. This variable is set to the function which mu4e will use.

By default, mu4e will use ido (via 'ido-completing-read'), but any
compatible completing-read function can be used instead. Interesting
choices would include 'helm-comp-read' for Helm-based completion, and
'completing-read' for the built-in basic completion system.
Merge branch 'develop' of github.com:hickinbottoms/mu into develop

Conflicts:
	mu4e/mu4e-utils.el
	mu4e/mu4e-vars.el