On Thursday May 19 2016,
cho...@chopps.org wrote:
> I'm getting more motivated to get this fixed, and started looking around
> in the code. The problem is that at some point after starting mu4e when
> I try and compose a new message or reply, contact completion returns no
> matches. Quiting and restarting mu4e fixes the issue.
>
> I haven't figured out what is going on; however, I do see that when I
> can't complete contacts the following is true:
>
> - mu4e~contacts is nil
>
> - (mu4e~proc-ping) generates and error:
>
> "error in process filter: mu4e~default-handler: Not handled: ((:crypto t :guile t :version "0.9.16" :doccount 194716))
> error in process filter: Not handled: ((:crypto t :guile t :version "0.9.16" :doccount 194716))"
>
> This might be normal but when I do this when things are working it
> flips me from scratch to the main mu4e view.
>
> Can you suggest other things to check for when I encounter the issue
> again?
That narrows things down... what seems to happen is the that the handler
function for "pong" responses is not what it should be. This handler is
set in mu4e~start, and this apparently works when (re)starting mu4e. The
function is never un-set, but apparently (from the data above), it seems
it _is_ unset somehow. Hmmm...
Are any other errors reported in the *Messages* buffer before the time
before the symptoms appear? Are perhaps any third-party modules that
interact with mu4e involved?