-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[mu4e] multiple account setup doesn't work as documented #4670
Comments
I ran into this "bug" recently too. The mu4e layer expects
|
Clarify usage for multiple accounts, as discussed by @darkfeline in syl20bnr#4670
thanks, that fixed it =) |
@andreas-h @darkfeline FYI I tweaked this behavior in the past here: ea9ce5e I only used a single email account, and I didn't want to be bothered to define this special Seems like there's still some room for improvement here where we wouldn't have to pre-define this value in the layer declaration, but this is a step in the right direction. |
Clarify usage for multiple accounts, as discussed by @darkfeline in #4670
Not sure if ya'll want a new issue created, but the docs should be updated in any case to use the new Contexts feature in the latest stable mu4e release. |
I think we can rip out the multiple account support entirely with the new mu4e-contexts feature. I'll create a PR for it. Here: #4836 |
Clarify usage for multiple accounts, as discussed by @darkfeline in syl20bnr#4670
Fixed with released of Spacemacs v0.200. Let us know if you still have any problems with this issue. |
@TheBB @darkfeline @nwolfe
For me, the multiple account setup doesn't work as advertised. In my
init.el
, I have the following:Apparently,
mu4e-account-alist
is not defined yet at the end of the mu4e layer'spackage.el
. At least, when I modify the last lines ofpackage.el
to readI only get the first
message
in my*messages*
buffer, and not the second one. However, when Ieval
those lines in the*scratch*
buffer afterwards, I get both messages.Any help in resolving this is greatly appreciated =)
The text was updated successfully, but these errors were encountered: