From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: 44509@debbugs.gnu.org
Subject: bug#44509: 28.0.50; Error querying with new gnus-search and notmuch
Date: Wed, 11 Nov 2020 05:10:49 +0000 [thread overview]
Message-ID: <875z6cxyue.fsf@gnus.jao.io> (raw)
In-Reply-To: <87imag7kkh.fsf@gnus.jao.io>
Hi again, Eric.
I was looking at the notmuch engine code and wondering why it wasn't
working for me in a leafnode directory, which puts its messages in a
nnmail-compatible format (as far as i can tell). And i discovered what
looks like a possible bug in gnus-search-indexed (or a misunderstanding
on my side). Concretely, on line 1363 of gnus-search, when implementing
gnus-search-indexed-parsed output, we're constructing a groups regexp
that looks like:
(group-regexp (when groups
(regexp-opt
(mapcar
(lambda (x) (gnus-group-real-name x))
groups))))
and then matching the returned list of files on that regexp (line 1377):
(string-match-p group-regexp f-name)))
But gnus-group-real-name is giving me back a dot-separated path for
nested folders (e.g. gmane.bugs.gnus), while the file paths in the
results are using slashes (gmane/bugs/gnus/234 etc.), so the match
test always fails and no results are returned.
If i simply redefine group-regexp using:
(replace-regexp-in-string "\\." "/" (gnus-group-real-name x)))
searches work fine for me. I can do that with an around advice, so that
my tricks work in this case, but i was wondering if it's an oversight.
On other news, i was trying to find a way in Gnus to go from Message-ID
to article no. for IMAP groups or nnmaildirs (which would make using
notmuch with dovecot really trivial), but without luck: anyone knows of
an easy way?
Cheers,
jao
--
As I grow to understand life less and less, I learn to live it more and
more.
-Jules Renard, writer (1864-1910)
next prev parent reply other threads:[~2020-11-11 5:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 1:44 bug#44509: 28.0.50; Error querying with new gnus-search and notmuch Jose A. Ortega Ruiz
2020-11-08 2:23 ` Eric Abrahamsen
2020-11-08 2:49 ` Jose A. Ortega Ruiz
2020-11-08 4:53 ` Eric Abrahamsen
2020-11-08 7:09 ` Jose A. Ortega Ruiz
2020-11-11 5:10 ` Jose A. Ortega Ruiz [this message]
[not found] ` <uMxcF8JPFQWri9-dIaeTgjGDP3ACtDZ1GqktYJqUzsD2Yh3axLc8KfS50JxW0gyoZYNJsPwSC_j0rx-q8W9AVw==@protonmail.internalid>
2020-11-11 17:51 ` Eric Abrahamsen
2020-11-11 17:56 ` Eric Abrahamsen
2020-11-11 18:29 ` jao
2020-11-11 19:11 ` Eric Abrahamsen
2020-11-11 21:50 ` jao
2020-11-12 0:29 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875z6cxyue.fsf@gnus.jao.io \
--to=jao@gnu.org \
--cc=44509@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).