I added the following definitions to my init.el file, which seems to solve the
problem:
(defun org-notmuch-search-open (path _)
"Follow a notmuch search link specified by PATH."
(notmuch-search path notmuch-search-oldest-first
notmuch-search-hide-excluded))
(defun
erik colson writes:
>
> Thanks for the hint, but tried setting the var with setq-default, but
> still same issue.. :
>
> notmuch-search-hide-excluded is a variable defined in ‘notmuch-lib.el’.
>
> Its value is nil
> Original value was t
> Local in buffer *notmuch-saved-tree-1week and
David Bremner writes:
> It might matter how you are setting notmuch-search-hide-excluded. It
> is buffer-local (that changed recently, I think) so you need to either
> use customize or setq-default.
Hi,
Thanks for the hint, but tried setting the var with setq-default, but
still same issue.. :
erik colson writes:
> Hi,
>
> I recently upgraded from an older version in which excluded tags in the
> notmuch config were nicely hidden. Now I have exactly the same problem
> as Stanton described. I can see notmuch-search-hide-excluded is set
> globally to t, but in every search buffer it
David Bremner writes:
> 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
>>
In case anyone else is affected by this, the problem I was having was that
notmuch-search org links (defined in ol-notmuch.el) were returning results that
included spam and trash messages even though I had asked to exclude these. To
get around this, redefine org-notmuch-search-open to
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"
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
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, 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 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
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 into my *scratch* buffer and execute
13 matches
Mail list logo
