Actually, I think the code might be working as intended. Calling notmuch-search
interactively things work just fine, and in the comments I see the note
"When called interactively, this will prompt for a query and use the configured
default sort order.”
This sounds like it deliberately ignores
I used edebug to trace through the execution of notmuch-search in notmuch.el.
At line 1096, we have the code
(let ((proc (notmuch-start-notmuch
"notmuch-search" buffer #'notmuch-search-process-sentinel
"search" "--format=sexp" "--format-version=5"
Running
(notmuch-search "tag:unread" t t)
gives the correct results, so it looks like notmuch-search-hide-excluded is not
getting set to the correct default value.
> On Apr 16, 2024, at 3:15 PM, Richard H. Stanton
> wrote:
>
> Oh, wait… It's not working on my office machine either. I’ll sta
Oh, wait… It's not working on my office machine either. I’ll start tracing
things and see what happens.
By the way,
(notmuch-config-get "search.exclude_tags”)
returns
"spam
trash"
which is what it should be returning.
> On Apr 16, 2024, at 12:00 PM, Richard H. Stanton
> wrote:
>
> Thanks,
Thanks, David.
It all seems to be working fine on my work machine!
I can’t decide if that’s good or bad news… I suspect it’ll take me longer to
track down what’s going on than if the behavior were consistent on my two
machines.
> On Apr 16, 2024, at 7:23 AM, David Bremner wrote:
>
> Richard
Richard Stanton writes:
> I have spam and trash defined as excluded tags for notmuch searches and when
> I run (at the command line) the command
>
> notmuch search tag:unread
>
> I get a list of unread messages that does *not* include unread spam or trash
> emails. But when I put the following
