Alasdair McAndrew <
amc...@gmail.com> writes:
> Thanks, Stig. Well, I'm still having problems:
>
> 1. No matter which context I choose, I can only see messages from the
> "Home" context. For example: "bu" for unread messages shows me Home
> messages only no matter what context I choose.
> 2. I'm only seeing messages from December 30 and before.
> 3. "Update email & database" produces the error: "error in process
> sentinel: muserver process received signal 11" which would seem to indicate
> that something is amiss,but I'm not sure what. I've tried to follow the
> instructions at
https://github.com/djcb/mu/issues/631 but gdb claims that
> mu isn't running.
It sounds like the last issue is key. If mbsync doesn't finish cleanly,
I'm guessing mu won't index the mailboxes ergo you won't see any new
messages. (Mu is heavily reliant on index, rather than looking at the
mailbox if I understand correctly.)
Perhaps mbsync does not run properly from within emacs (either because
of issue with path, or because it can't get passwords from keychain,
depending on how you've configured it?) Here's how to test this:
1. Set =mu4e-get-mail-command= to "true" in both contexts (or remove
the setting from your context vars and set it outside)
2. Stop emacs/mu4e
3. Run =mbsync -a= outside emacs, to ensure it works
4. Start emacs/mu4e
5. Hit "U" in the menu
6. Enter any of the bookmarks
If things now work, you should have an avenue for testing. One trick
I've seen some people use is setting =mu4e-get-mail-command= to
"mbsync -a || true" to let it run, but not get stuck if it fails. I am
using GNU coreutils' timeout (gtimeout on a Mac) to kill mbsync after
60 seconds if it misbehaves.
If bookmarks *don't* work for you now, perhaps something is wrong with
the context switching instead. In that case, do you see the context
switching messages you have configured? ("entering ... " "Leaving...")
If not, what does this command say? It *should* print the current
context name to the minibuffer.
: M-: (mu4e-context-name (mu4e-context-current)) RET
Try that and switch context, then try it again. If the context names
change, your context switches is probably not the issue.
You can also verify this by setting different custom jump commands in
each context and checking whether they are as you expect after
changing context. (The config I linked to earlier has examples of
that.) Another way would be to change bookmarks in the contexts and
perusing the bookmarks with "B".
> I know that all messages are being properly downloaded, as mutt can find
> them all. I've clearly made a hash of my contexts, although I've tried
> to follow the directions in the manual as well as I can.
Personally I don't think your contexts are the issue, rather that mu
is not indexing your messages.
Stig