[GH-ISSUE #34] [Enhancement] Filter message list by read status #33

Closed
opened 2026-03-03 01:19:13 +03:00 by kerem · 4 comments
Owner

Originally created by @Kabouik on GitHub (Feb 18, 2020).
Original GitHub issue: https://github.com/d99kris/nmail/issues/34

Originally assigned to: @d99kris on GitHub.

I'm back (and will soon follow-up on the issues you updated lately), already bothering you with new feature requests!

It would be nice to have the possibility to show only [Unread] emails in the message list for faster sorting when late with email reading. I don't know if this should be a standalone feature or if it should be just one of the possibilities of the email search feature (read/unread could be a tag to be searched for) when it is implemented, but this is a big milestone.

Originally created by @Kabouik on GitHub (Feb 18, 2020). Original GitHub issue: https://github.com/d99kris/nmail/issues/34 Originally assigned to: @d99kris on GitHub. I'm back (and will soon follow-up on the issues you updated lately), already bothering you with new feature requests! It would be nice to have the possibility to show only [Unread] emails in the message list for faster sorting when late with email reading. I don't know if this should be a standalone feature or if it should be just one of the possibilities of the email search feature (read/unread could be a tag to be searched for) when it is implemented, but this is a big milestone.
kerem closed this issue 2026-03-03 01:19:14 +03:00
Author
Owner

@d99kris commented on GitHub (Feb 19, 2020):

Right, this functionality would make sense to have. Let me think about the UI, but I'd think it would fit in a some filter/sort functionality, separate from search.

<!-- gh-comment-id:588159105 --> @d99kris commented on GitHub (Feb 19, 2020): Right, this functionality would make sense to have. Let me think about the UI, but I'd think it would fit in a some filter/sort functionality, separate from search.
Author
Owner

@d99kris commented on GitHub (Feb 27, 2021):

Hi, I finally got a chance to look at this now. In the above commit I've implemented basic support for message list filtering. ! will show only unread messages, @ will show only messages with attachments. The idea behind these default key mappings is that unread status is indicated in column 1 (shift 1 on US keyboard is !), etc.

The message filter list is not dynamically updated. If a new message arrives and one has filtering on, one needs to toggle the filter off/on again, for the filtered message list to refresh. So in a sense the filter behaviour is similar to message search, where the user gets a snapshot of the matching messages at that point in time. The reason for this is mainly to minimize the complexity of the code.

Let me know if you encounter any issues with the filtering. Thanks!

<!-- gh-comment-id:787029534 --> @d99kris commented on GitHub (Feb 27, 2021): Hi, I finally got a chance to look at this now. In the above commit I've implemented basic support for message list filtering. `!` will show only unread messages, `@` will show only messages with attachments. The idea behind these default key mappings is that unread status is indicated in column 1 (shift 1 on US keyboard is `!`), etc. The message filter list is not dynamically updated. If a new message arrives and one has filtering on, one needs to toggle the filter off/on again, for the filtered message list to refresh. So in a sense the filter behaviour is similar to message search, where the user gets a snapshot of the matching messages at that point in time. The reason for this is mainly to minimize the complexity of the code. Let me know if you encounter any issues with the filtering. Thanks!
Author
Owner

@Kabouik commented on GitHub (Feb 27, 2021):

I wouldn't have expected the list to refresh dynamically when filtering so that sounds perfect to me, thank you for delivering this and making nmail better and better so fast. Great surprise to get a filter for attachments as well!

On 2021-02-27 08:27 Kristofer Berggren notifications@github.com wrote:

Hi, I finally got a chance to look at this now. In the above commit I've implemented basic support for message list filtering. ! will show only
unread messages, @ will show only messages with attachments. The idea behind these default key mappings is that unread status is indicated in
column 1 (shift 1 on US keyboard is !), etc.

The message filter list is not dynamically updated. If a new message arrives and one has filtering on, one needs to toggle the filter off/on
again, for the filtered message list to refresh. So in a sense the filter behaviour is similar to message search, where the user gets a snapshot
of the matching messages at that point in time. The reason for this is mainly to minimize the complexity of the code.

Let me know if you encounter any issues with the filtering. Thanks!

--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/d99kris/nmail/issues/34#issuecomment-787029534

<!-- gh-comment-id:787047518 --> @Kabouik commented on GitHub (Feb 27, 2021): I wouldn't have expected the list to refresh dynamically when filtering so that sounds perfect to me, thank you for delivering this and making nmail better and better so fast. Great surprise to get a filter for attachments as well! On 2021-02-27 08:27 Kristofer Berggren <notifications@github.com> wrote: > Hi, I finally got a chance to look at this now. In the above commit I've implemented basic support for message list filtering. `!` will show only > unread messages, `@` will show only messages with attachments. The idea behind these default key mappings is that unread status is indicated in > column 1 (shift 1 on US keyboard is `!`), etc. > > The message filter list is not dynamically updated. If a new message arrives and one has filtering on, one needs to toggle the filter off/on > again, for the filtered message list to refresh. So in a sense the filter behaviour is similar to message search, where the user gets a snapshot > of the matching messages at that point in time. The reason for this is mainly to minimize the complexity of the code. > > Let me know if you encounter any issues with the filtering. Thanks! > > -- > You are receiving this because you authored the thread. > Reply to this email directly or view it on GitHub: > https://github.com/d99kris/nmail/issues/34#issuecomment-787029534
Author
Owner

@d99kris commented on GitHub (Feb 27, 2021):

Ok, that's great to hear!

<!-- gh-comment-id:787059563 --> @d99kris commented on GitHub (Feb 27, 2021): Ok, that's great to hear!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nmail#33
No description provided.