We modified the code a bit because mu4e links are somehow reserved for mu4e. You now have the option to name the link to whatever you want and the default is mu. I think you can set it back to mu4e but it might interfere with mu4e regular links.

from mu4e-dashboard.

replacine mu with mu4e worked.

A question related to count:
this works
mu:from:[email protected]|%3d

but not this
mu:(date:4w..now AND from:[email protected])|%3d

this displays a "+" symbol instead of count.

Is count is not expected to work with compound queries? @rougier

from mu4e-dashboard.

It depens on the count. Since you give %3d for format and if the number is higher, it will display "+++" to indicate that the count is higher. Try with %5d for example. But it seems there's a bug for some peopel (see #19)

from mu4e-dashboard.

@rougier thanks for the update,

I tried few things , the issue is not about using %5d because my email numbers are not that big. What I found out is

Using braces was the problem

mu:(date:today..now AND from:[email protected])|%3d

this worked:

mu:date:today..now AND from:[email protected]|%3d

Update:

e.g. In this

[[mu:(date:today..now AND from:[email protected])][today]][[mu:(date:today..now AND from:[email protected])|%3d][  0]] 

clicking on today opens expected mu4e buffer with emails as expected but the count part is getting displayed as zero.
Braces works in the link but not in the count.

from mu4e-dashboard.

Thanks for the report. I think the braces are interpreted by the shell when we make the call:

$ mu find date:today..now | wc -l
9
$ mu find "(date:today..now)" | wc -l
9
$ mu find (date:today..now) | wc -l
zsh: number expected
0

Can you confirm? If so, it's a matter of surrounding the query with \" in the shell call. Could you make a PR?

from mu4e-dashboard.