Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: How to rescan just one group?
Date: 25 Mar 2001 12:41:56 +0200	[thread overview]
Message-ID: <vafitkyuo3v.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3d7b63omg.fsf@fermat.mts.jhu.edu> (Nevin Kapur's message of "24 Mar 2001 15:20:39 -0500")

On 24 Mar 2001, Nevin Kapur wrote:

> I don't think grepmail can do this, but it should be easy enough to
> write perl that does it. But,
> 
> ,----[ From nnir.el ]
> | ;; Restrictions:
> | ;;
> | ;; * Currently, this expects that you use nnml or another
> | ;;   one-file-per-message backend.
> | ;; * It can only search one mail backend.
> `----
> 
> I archive my mail using nnfolder. I also want to search both nnml
> and nnfolder. I've hacked grepmail so that it works with nnml style
> folders.

I wish I had the time to implement multi-backend searching for
nnir.el.  I know how to implement part of it already: just add server
parameters for nnir-search-engine and so on and have the searching
functions iterate over all the backends and invoke the backend search
function (nnir-run-query) for each backend.  What I don't know how to
implement is the group marking; you can process-mark a couple of
groups then issue a query, the query is restricted to the groups.
Probably what needs to be done is to go over all the servers, then
fetch the list of process-marked groups from each server, then invoke
nnir-run-query for that list.  Yes, that should work.

The restriction to `one file per message' backends is an artefact of
the searching mechanisms, the real restriction is in the interface, as
you cite below:

> ,----[ Later on in nnir.el ]
> | ;; The interface between the two layers consists of the single
> | ;; function `nnir-run-query', which just selects the appropriate
> | ;; function for the search engine one is using.  The input to
> | ;; `nnir-run-query' is a string, representing the query as input by
> | ;; the user.  The output of `nnir-run-query' is supposed to be a
> | ;; vector, each element of which should in turn be a three-element
> | ;; vector.  The first element should be group name of the article, the
> | ;; second element should be the article number, and the third element
> | ;; should be the Retrieval Status Value (RSV) as returned from the
> | ;; search engine.  An RSV is the score assigned to the document by the
> | ;; search engine.  For Boolean search engines like Glimpse, the RSV is
> | ;; always 1000 (or 1 or 100, or whatever you like).
> `----
> 
> So, if the output of nnir-run-query returned a vector that contained
> group names that were nnfolder groups, would it be OK?

Yes, that would be okay.

kai
-- 
Be indiscrete.  Do it continuously.


  reply	other threads:[~2001-03-25 10:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-24  2:16 Nevin Kapur
2001-03-24 20:01 ` Kai Großjohann
2001-03-24 20:20   ` Nevin Kapur
2001-03-25 10:41     ` Kai Großjohann [this message]
2001-03-25 11:22 ` Gregory.Chernov

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=vafitkyuo3v.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).