Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: nnir UI
Date: 15 Oct 1999 13:08:56 +0200	[thread overview]
Message-ID: <vafemewswxj.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Jens-Ulrik Petersen's message of "15 Oct 1999 18:14:41 +0900"

Jens-Ulrik Petersen <jens-ulrik.petersen@nokia.com> writes:

> No, no, probably I'm just being stupid.  
> 
> Well actually yes, I get the following error when I try to use nnir
> (v1.45) with nnimap-0.130.
> 
>   error("Must specify groups for IMAP searching.")

This means that you should use `#' to process-mark a couple of groups
to search in.  This is required because searching in all groups is way
too slow with most IMAP servers.

> To be find the UI/setup of nnir a bit unfriendly.  Why not just use
> the backend on the current line for the search by default?  Why do I
> need to change a variable to search a different backend?

Simon has sent me a patch for choosing the right backend
automatically.  Hm.  Maybe I forgot to include it in nnir.el -- sorry,
Simon.

There is a historical reason for nnir.el not choosing the right
backend automatically.  I designed it to work with search engines
(freeWAIS-sf and Glimpse, at first), and for them you have to create
an index over your mail files first.  Obviously, the index only covers
a certain backend, so I required users to choose the backend manually.

I did come across the problem that this method does not (easily) allow
people to use two different indexes, possibly even over two different
backends.  Hm.  I thought that most people have stored all their mail
in one backend, anyway, so such a feature would not be necessary.  And
this choice was before there was the feature of process-marking some
groups to search in.  Back then, I was using nnml exclusively (with a
freeWAIS-sf index).  Now, I use nnimap and I find that the need to
process-mark groups to search in is rather inconvenient.  But with
IMAP, searching should be implemented on the server side, it seems.  I
intend to do some work on Cyrus for better integration with a search
engine, but I'm not promising anything, right now!  And the query
language specified in the IMAP protocol is not what is desirable from
an IR point of view.  Oh, well...  (I guess that Lotus Notes already
provides nice searching capabilities -- any Notes users out there?
Didn't the Notes people also violate the IMAP standard in order to
provide for better searching?)

I do intend to get back to work on nnir some time in the future, so
don't hesitate to contact me about new ideas, and I'll try to file
them away for later looking at them, when I have time.

kai
-- 
Life is hard and then you die.


      parent reply	other threads:[~1999-10-15 11:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-13  1:07 [patch] doc typo Jens-Ulrik.Petersen
1999-10-13 12:38 ` Simon Josefsson
1999-10-15  9:14   ` nnir UI Jens-Ulrik Petersen
1999-10-15 11:03     ` Simon Josefsson
1999-10-15 11:25       ` Kai Großjohann
1999-10-15 11:08     ` Kai Großjohann [this message]

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=vafemewswxj.fsf@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).