Sean Whitton <spwhitton@spwhitton.name> writes:
> Hello,
>
> I'm running a pretty innocent notmuch query over a fairly small Maildir:
>
> "((List:debian-devel.lists.debian.org) or ... or
> (List:debian-haskell.lists.debian.org) or
> (List:debconf-discuss.lists.debian.org)) and (not path:annex/**)"
>
> but gnus-search-run-search fails to return any results. The reason is
> that Gnus first runs the query with --output=threads to obtain a list of
> thread ids, and then runs another query with --output=files and a query
> constructed from the output of the first query: "thread:000000000000d9d0
> or thread:000000000000d9e0 or thread:000000000000d268 or ..."
>
> The resulting command fails completely:
>
> emacs: /usr/bin/notmuch: Argument list too long
>
> Instead of running two searches like this, we can just surround the
> whole query like this: "thread:{QUERY}". The manual says it's exactly
> equivalent:
>
> ... the user should think of the query thread:{<something>} as
> expanding to all of the thread IDs which match <something>; not‐
> much then performs a second search using the expanded query.
>
> This should be faster, too, with only running a single external command.
> Here is the patch I'm thinking I'll apply, if anyone has comments.
Huh, I tried this a couple months ago with a more complicated query,
like:
thread:{from:bob or from:jane}
and I remember notmuch barking at me about spaces or the "or" or
something -- anyway I got the impression that it couldn't accept
multi-part queries inside the "thread:{}" syntax. But looking at your
patch maybe I just needed to quote differently?
Anyway I'll give this a test this weekend. It would be *very* nice if we
could use this syntax rather than the ugly home-grown one.
Thanks for the report!
Eric\r
Hello, On Sat 09 Jul 2022 at 09:11AM -07, Eric Abrahamsen wrote: > But looking at your patch maybe I just needed to quote differently? Right, notmuch has this unusual " -> "" quoting thing. > Anyway I'll give this a test this weekend. It would be *very* nice if > we could use this syntax rather than the ugly home-grown one. Let me know the results of your test, and if it's also continuing to work for me by then, I'll install the change. Thanks for taking a look. -- Sean Whitton
On Sat, Jul 09 2022, Eric Abrahamsen wrote: > > Huh, I tried this a couple months ago with a more complicated query, > like: > > thread:{from:bob or from:jane} > > and I remember notmuch barking at me about spaces or the "or" or > something -- anyway I got the impression that it couldn't accept > multi-part queries inside the "thread:{}" syntax. But looking at your > patch maybe I just needed to quote differently? I am not sure whether this is relevant, but I give a shot... I tried the following queries from command line: $ notmuch search 'thread:"{from:bob or from:jane}"' thread:0000000000000b91 2009-01-20 [6/6] ... thread:00000000000015fa 2008-11-26 [2/2] ... and $ notmuch search 'from:bob or from:jane}': thread:0000000000000b91 2009-01-20 [1/6] ... thread:00000000000015fa 2008-11-26 [1/2] ... The outer '':s protect from shell expansion so what is inside those goes verbatim to notmuch and from there to xapian query parser (IIRC). Former includes all messages in thread where at least one message matched to the query and latter just those messages that match the query. Like Sean mentioned in another message, Xapian converts "" to " in query string (probably something irrelevant in this discussion) the thread:"{...}" syntax binds the whole expression to this thread: prefix (Why {...} is not enough is beyond me ;D) Tomi > > Anyway I'll give this a test this weekend. It would be *very* nice if we > could use this syntax rather than the ugly home-grown one. > > Thanks for the report! > > Eric