unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Torsten Bronger <bronger@physik.rwth-aachen.de>
Cc: 46047@debbugs.gnu.org
Subject: bug#46047: 28.0.50; Namazu-based mail searching not working anymore
Date: Sat, 23 Jan 2021 09:42:33 -0800	[thread overview]
Message-ID: <878s8j7do6.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87pn1wnsv0.fsf@physik.rwth-aachen.de> (Torsten Bronger's message of "Sat, 23 Jan 2021 06:07:47 +0100")

Torsten Bronger <bronger@physik.rwth-aachen.de> writes:

> Since commit 7fad12c59b3c65665c10050e800d1d7ad5a2e056, I have
> problems getting namazu-based mail searching working.  My
> configuration says:
>
> In .emacs:
>
> (setq nnir-namazu-index-directory "/var/lib/namazu/")
>
> In .gnus:
>
> (setq gnus-secondary-select-methods '((nnml "" (nnir-search-engine namazu))))
> ;; I have not set gnus-search-use-parsed-queries.
>
> This results in "Group nnselect:nnselect-87sg78bdzr.fsf contains no
> messages" error when I hit "G G" in the group buffer and enter a query
> string.  Besides, the namazu executable is not called at all.  The same
> behavour I get if I don’t configure namazu at all in Emacs/Gnus.

Thanks for the report. I haven't provided obsolete aliases for all of
the old nnir-<engine>-* variables, as that would be quite a pile, but if
that's annoying to enough people I can.

If you're not planning to revert to an earlier Emacs, it would be
easiest just to switch to setting `gnus-search-namazu-index-directory'.
If you are planning to revert, you could always set both. Alternately,
you could set the index directory within the server definition itself,
like so:

'((nnml "" (nnir-search-engine namazu
             (nnir-namazu-index-directory "/var/lib/namazu/"))))

I haven't yet added backwards compatibility code to honor that server
parameter, but I could do so fairly easily, then this config would be
past-and-future proof.

It's a little suspicious that the namazu program isn't getting called at
all, though. The code essentially just calls:

(start-process "name" <buffer> "namazu")

If "namazu" is on your path, it should be found.

Would you try setting the newer index-directory variable, just to
eliminate that as a source of error?

nnselect-run currently downgrades errors to messages (then reports no
messages found), so if there's really something blowing up, you might
see it in your *Messages* buffer.

Eric





  reply	other threads:[~2021-01-23 17:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-23  5:07 bug#46047: 28.0.50; Namazu-based mail searching not working anymore Torsten Bronger
2021-01-23 17:42 ` Eric Abrahamsen [this message]
2021-01-23 20:17   ` Torsten Bronger
2021-01-23 22:14     ` Eric Abrahamsen
2021-01-23 22:26       ` Eric Abrahamsen
2021-01-25 10:10         ` Torsten Bronger
2021-02-07 22:02           ` Eric Abrahamsen
2021-02-12 13:53             ` Torsten Bronger
2021-02-12 15:25               ` Torsten Bronger
2021-04-21  3:19                 ` Stefan Kangas
2021-05-09 14:21                   ` Torsten Bronger
2021-05-12 18:18                     ` Eric Abrahamsen
2021-05-16 17:24                     ` Eric Abrahamsen
2021-05-16 19:43                       ` Torsten Bronger
2021-05-16 22:11                         ` Eric Abrahamsen
2021-05-17  6:02                           ` Torsten Bronger
2021-05-17 18:53                             ` Eric Abrahamsen
2021-05-18  8:46                               ` Torsten Bronger
2021-05-18  9:08                                 ` Eli Zaretskii
2021-05-18 16:50                                   ` Eric Abrahamsen
2021-05-18 16:55                                     ` Eli Zaretskii
2021-05-21 17:47                                       ` Eric Abrahamsen
2021-05-21 19:10                                         ` Torsten Bronger
2021-05-21 20:38                                           ` Eric Abrahamsen
2021-01-23 22:30       ` 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=878s8j7do6.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=46047@debbugs.gnu.org \
    --cc=bronger@physik.rwth-aachen.de \
    /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).