From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: problem with notmuch search in recent emacs snapshots
Date: Sat, 17 Nov 2018 18:28:31 +0000 [thread overview]
Message-ID: <87d0r3imnk.fsf@ucl.ac.uk> (raw)
Hello,
recently, I upgraded my emacs to the latest snapshot (20181111) on
Debian. Since then, search in gnus does not work. It always fails. An
example of the messages that are generated follows:
--8<---------------cut here---------------start------------->8---
Doing notmuch query XXX on mail.misc mail.gemini mail.t3610 mail.pinto...
notmuch args: search --format=text --output=files XXX( path:mail.misc or path:mail.gemini or path:mail.t3610 or path:mail.pinto)
Massaging notmuch output...done
Search produced empty results.
gnus-select-newsgroup: Couldn’t request group nnir:nnir-87lg5rindf.fsf: Search produced empty results.
--8<---------------cut here---------------end--------------->8---
With the exact same gnus and notmuch configuration, everything is fine
with emacs snapshots from a couple of months ago; one of my systems is
running snapshot 20180909. There is one obvious difference: the notmuch
arguments, for the same search, at the same topic, looks like this:
notmuch args: search --format=text --output=files XXX
I.e. no paths are specified.
I wonder whether the problem is the strange lack of a space between XXX
(my search term) and the opening "(" for the list of paths to check?
Even if only a single group is checked, the latest versions of gnus
append an explicit path.
If I turn nnir-notmuch-filter-group-names-function to nil, I get the old
behaviour back so I can still search but the default does not appear to
work.
Adding a space before "(" on line 1547 of nnir.el might fix this?
Untested.
thanks,
eric
--
Eric S Fraga via Emacs 27.0.50 & org 9.1.14 on Debian buster/sid
next reply other threads:[~2018-11-17 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 18:28 Eric S Fraga [this message]
2018-11-17 18:44 ` Eric Abrahamsen
2018-11-18 11:45 ` Eric S Fraga
2018-11-18 18:59 ` Eric Abrahamsen
2018-11-19 8:36 ` Eric S Fraga
2018-11-21 16:53 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0r3imnk.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).