#20 notmuch search over whole database

Open
opened 4 months ago by cycomanic · 3 comments

Maybe I’m doing something wrong see the attached video (not sure what filetypes I can upload, so zipped again). I have two virtual mailboxes:

“todo1” = { query="tag:todo and date:..2020-01-01”, subscribe = true }
“todo2” = { query="tag:todo and date:2020-01-01..", subscribe = true }

When I do a search while inside todo1 for date:2020-01-02.. I get 0 results, should I not see the results form todo2 as well if it searches over the whole notmuch database?

Maybe I'm doing something wrong see the attached video (not sure what filetypes I can upload, so zipped again). I have two virtual mailboxes: "todo1" = { query="tag:todo and date:..2020-01-01", subscribe = true } "todo2" = { query="tag:todo and date:2020-01-01..", subscribe = true } When I do a search while inside todo1 for date:2020-01-02.. I get 0 results, should I not see the results form todo2 as well if it searches over the whole notmuch database?
755 KiB
epilys commented 4 months ago
Owner

Oops, that was clearly my misunderstanding. The search indeed is not mailbox related, but when the results are displayed in the mailbox they are filtered to show only the results inside the mailbox. I’m sorry!

There should be a more versatile search interface that allows one to search whatever they want.

Oops, that was clearly my misunderstanding. The search indeed is not mailbox related, but when the results are displayed in the mailbox they are filtered to show only the results inside the mailbox. I'm sorry! There should be a more versatile search interface that allows one to search whatever they want.
cycomanic commented 4 months ago
Poster

OK I thought I was doing something wrong. Regarding a search interface, I suggest doing two separate commands (.e.g search and query) for the two use cases.

OK I thought I was doing something wrong. Regarding a search interface, I suggest doing two separate commands (.e.g search and query) for the two use cases.
epilys commented 4 months ago
Owner

Regarding a search interface, I suggest doing two separate commands (.e.g search and query) for the two use cases.

I initially called it filter since it filters the mailbox list, but then I wanted to reuse the command for searching within text.

query makes sense since it’s also what defines a virtual mailbox. I will introduce unified mailboxes at some point, which will essentially be virtual mailboxes but for all backends/accounts. That way you can have for example one Inbox for all your accounts pinned to the top of the menu.

> Regarding a search interface, I suggest doing two separate commands (.e.g search and query) for the two use cases. I initially called it `filter` since it filters the mailbox list, but then I wanted to reuse the command for searching within text. `query` makes sense since it's also what defines a virtual mailbox. I will introduce unified mailboxes at some point, which will essentially be virtual mailboxes but for all backends/accounts. That way you can have for example one Inbox for all your accounts pinned to the top of the menu.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.