~soywod/pimalaya#63: 
Add unseen message counter column in folder listing

I have server side rules which syphons off unread emails to different folders. Not all my unread emails are in the INBOX when I sync. How can I view where these unread emails are? Is there a way to mark them as read all at once?

If I use search -- not seen, it will only show me the emails, but now what folders they're in. I think this would be the easiest fix: add a "folder" field to the messages that search returns, so I can see where they all are at.

Then I could search for all emails, and then a script could filter out the ones that aren't in the inbox and grab their IDs, using another himalaya command to mark them all as read :)


  • Implement WithUnseenMessagesCount<T> struct and ListFoldersWithUnseenMessagesCount feature trait.
  • Implement feature for IMAP.
  • Implement feature for Maildir.
  • Implement feature for Notmuch.
  • Update BackendBuilder to accept this new feature.
Status
REPORTED
Submitter
~skin
Assigned to
No-one
Submitted
6 months ago
Updated
17 days ago
Labels
1:email-lib 2:himalaya 3:cli

~soywod 6 months ago

I have server side rules which syphons off unread emails to different folders. Not all my unread emails are in the INBOX when I sync.

[…]

If I use search -- not seen, it will only show me the emails, but now what folders they're in.

Something bothers me here, because when you list (or search) emails, you list them from a specific folder. search -- not seen will show all not seen emails from the INBOX folder. So the folder field will always be INBOX for all those emails.

Another approach could be to add a "unread" column to the folder listing that shows the number of emails not having the Seen flag, what do you think?

~soywod 6 months ago

~skin 6 months ago

Another approach could be to add a "unread" column to the folder listing that shows the number of emails not having the Seen flag, what do you think?

That would solve my problem nicely :)

-- Dan Haskin

~soywod 6 months ago

Let's go for it then!

Register here or Log in to comment, or comment via email.