From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Mailing lists and news archiving
Date: Sun, 20 Jan 2002 18:27:38 +0100 [thread overview]
Message-ID: <vafd7059blh.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3vgdyun41.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 19 Jan 2002 21:01:02 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Is nnir ready for inclusion in Gnus, you think?
It seems that the functionality that's offered by nnir.el is stable
and works okay. Maybe it's not enough functionality. Things that
come to mind:
* nnir only supports one backend to search in, because it's got a
global variable for the backend. I wanted to add server parameters
so that the nnir-specific things can be specified for each server,
and nnir would search all servers which are nnir-enabled. But I
haven't got around to it :-(
* nnir is kinda restricted to one-file-per-message backends. This is
because nnir calls a search engine, and tries to glean group name
and article number from that output. And it is easy to tell the
search engine to print the file name (wherefrom said data can
easily be gleaned). If you can convince the search engine to print
the article number and group name for other backends, then they
will work with nnir, too.
For example, nnimap works with nnir, because IMAP has a built-in
search command.
* nnir is kinda fragile because it parses the output of the
command-line search tools. So it's easy to confuse nnir by adding
a slash at the end of a directory name, or by removing it.
So: after a day of hacking by Lars the Quick Typist, I'm sure it will
be in good shape :-)
kai
--
Simplification good! Oversimplification bad! (Larry Wall)
next prev parent reply other threads:[~2002-01-20 17:27 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 19:36 Lars Magne Ingebrigtsen
2002-01-05 19:57 ` Lars Magne Ingebrigtsen
2002-01-05 21:00 ` news
2002-01-05 21:06 ` news
2002-01-05 21:36 ` Lars Magne Ingebrigtsen
2002-01-05 22:12 ` news
2002-01-06 7:13 ` Steinar Bang
2002-01-06 8:57 ` Lars Magne Ingebrigtsen
2002-01-06 14:13 ` Kai Großjohann
2002-01-19 20:01 ` Lars Magne Ingebrigtsen
2002-01-20 17:27 ` Kai Großjohann [this message]
2002-01-20 17:34 ` Lars Magne Ingebrigtsen
2002-01-20 17:38 ` Lars Magne Ingebrigtsen
2002-01-20 17:55 ` Lars Magne Ingebrigtsen
2002-01-20 21:33 ` Björn Torkelsson
2002-01-20 21:37 ` Lars Magne Ingebrigtsen
2002-01-22 1:23 ` Steve Youngs
2002-01-22 1:37 ` Lars Magne Ingebrigtsen
2002-01-22 2:23 ` Steve Youngs
2002-01-20 20:48 ` Steve Youngs
2002-01-20 17:35 ` Simon Josefsson
2002-01-06 2:09 ` Russ Allbery
2002-01-06 9:07 ` Lars Magne Ingebrigtsen
2002-01-08 12:52 ` Per Abrahamsen
2002-01-09 3:06 ` Russ Allbery
2002-01-09 10:55 ` Per Abrahamsen
2002-01-09 11:45 ` Russ Allbery
2002-01-19 20:04 ` Lars Magne Ingebrigtsen
2002-01-20 5:06 ` Karl Eichwalder
2002-01-05 22:47 ` Harry Putnam
2002-01-06 9:05 ` Lars Magne Ingebrigtsen
2002-01-06 9:52 ` Harry Putnam
2002-01-06 10:10 ` Lars Magne Ingebrigtsen
2002-01-06 10:23 ` Harry Putnam
2002-01-06 10:24 ` Lars Magne Ingebrigtsen
2002-01-06 10:40 ` Lars Magne Ingebrigtsen
2002-01-06 10:49 ` Lars Magne Ingebrigtsen
2002-01-06 11:25 ` Lars Magne Ingebrigtsen
2002-01-06 14:51 ` Karl Kleinpaste
2002-01-07 11:49 ` Colin Marquardt
2002-01-07 12:06 ` Lars Magne Ingebrigtsen
2002-01-07 18:13 ` Steinar Bang
2002-01-07 19:38 ` Lars Magne Ingebrigtsen
2002-01-08 9:06 ` Colin Marquardt
2002-01-06 12:42 ` Steinar Bang
2002-01-06 6:58 ` Steinar Bang
2002-01-06 9:13 ` Lars Magne Ingebrigtsen
2002-01-06 13:14 ` Frank Schmitt
2002-01-06 14:01 ` Florian Weimer
2002-01-06 15:38 ` Martin Thornquist
2002-01-07 7:58 ` Lars Magne Ingebrigtsen
2002-01-07 8:46 ` Simon Josefsson
2002-01-08 10:31 ` Fabien Penso
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=vafd7059blh.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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.
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).