Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: nnir/wais
Date: 20 Jun 2000 04:56:58 -0700	[thread overview]
Message-ID: <m28zw0a7lh.fsf@reader.ptw.com> (raw)

The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.


Posted to gnu.emacs.gnus and ding@gnus.org

Kai G has been very diligent about responding to any posts concerning
nnir.  

Are there any other readers here who are using freeWAIS as the engine for
nnir?

It seems that freeWAIS is not that easy to setup.  I know I've had
lots of trouble with it and still unable to get it working.  Although
Kai and another freeWAIS developer have helped well beyond the call of
duty.

I was able to get a short glimpse (pun intended) of the astounding
speed of freeWAIS in combination with nnir but have broken it somehow.
But I can report here that freeWAIS is easily several *hundred*
percentage points faster than glimpse.  

This post is a plea to users or interested parties of freeWAIS to
respond with any notes or tips that may help other users get freeWAIS
running as nnir engine.

Posting here seems like it would be appropriate for this group but if
interested parties would rather conduct private correspondence feel
free to do so.

The problems I've run into revolve around compiling the sources of
freeWAIS and once (sort of) compiled, getting it working from the
command line or with nnir.

This package is not well documented so something as simple as working
command lines for indexing and searching would be helpful.

The versions I've worked with are freeWAIS-2.1.13 and 2.1.14 available
at:
ftp://ls6-ftp.cs.uni-dortmund.de/pub/src/freeWAIS-sf/



                 reply	other threads:[~2000-06-20 11:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m28zw0a7lh.fsf@reader.ptw.com \
    --to=reader@newsguy.com \
    /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).