You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to show two, three, or more unread counts in my modeline.
In my case, one for work email, one for personal, and then a couple for high-priority mailing lists.
My mailbox currently has around 800k emails from many mailing lists. A lot of them are unread because they have no importance to me. As a consequence, a single "unread emails count" number doesn't work for me, because it will always be 99+.
I already filed the issue here iqbalansari/mu4e-alert#39
but MELPA tells me, this is the official repository :-)
The text was updated successfully, but these errors were encountered:
You are right, this is the upstream now. :) Your case is valid, but it's quite difficult to implement and will need a major redesign (mainly because of the lack of cooperation from mu4e author; due to that message fetching code is a mess of advices, callbacks and ad-hoc synchronization). I need a few days to consider possible implementations.
Meanwhile, you can tweak your mu4e-alert-interesting-mail-query customization variable to restrict the maildirs mu4e-alert looks into (that's what I do myself; my mu4e-alert-interesting-mail-query is "flag:unread and not flag:trashed and not maildir:/lists/ and not maildir:/promo/ and not maildir:/spam/ and not maildir:/todo/").
Hello,
I would like to show two, three, or more unread counts in my modeline.
In my case, one for work email, one for personal, and then a couple for high-priority mailing lists.
My mailbox currently has around 800k emails from many mailing lists. A lot of them are unread because they have no importance to me. As a consequence, a single "unread emails count" number doesn't work for me, because it will always be 99+.
I already filed the issue here
iqbalansari/mu4e-alert#39
but MELPA tells me, this is the official repository :-)
The text was updated successfully, but these errors were encountered: