Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: example queries for nnir
Date: 23 Jun 2000 16:50:55 -0700	[thread overview]
Message-ID: <m2r99o5540.fsf@reader.ptw.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 23 Jun 2000 14:33:19 +0200"

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:


[...]

> 
> My suggestion meant that you put all the words from the body into the
> global field, and no other words into the global field.  Hence
> searching the global field is the same as searching the body.


Hoookay now I get it... click!

> 
> > > Are you saying that (setq nnir-search-engine 'wais) and (setq
> > > nnir-search-engine 'imap) is not sufficient and that I should include
> > > the full list of allowed symbols?
> > 
> > Very sorry Kai, but I thought we were discussing the opening
> > comments in nnir.el.  Which should probably include the examples you
> > refer to above. Those that appear in that actual code as documnet
> > strings.  I had not noticed those examples which probably means many
> > new users would not either.
> 
> Hm.  Okay.  I have tried to explicitly include a pointer to the
> docstrings in the opening comments, but apparently this was not
> explicit enough.  Do you think a wording along the lines of `type C-h
> v nnir-search-engine RET for more information' would be clear enough?

Looking at version 1.57. It looks very clear... I even understood it..
he he

> Do you think it would be better to document it twice?  What about the
> newly changed wording in the opening comments?

After looking at the new stuff, and understanding better the reasoning
involved, I guess I was making a lot of fuss about nothing.  It seems
quite clear how to proceed now. 

> 
> > I think this is a good practice and was only suggesting that any of
> > the variables discussed in comments should also have any defaults
> > pointed out.
> 
> Okay.  FWIW, I have tried to make the variable documentation more
> explicit, too.

I see the new documentation.  Seems much more complete and usefull.
Thanks for being so responsive to this, even though I lack much skill
in this stuff.

Is that really true that wais needs:
`nnir-wais-remove-prefix'?  It doesn't default to /home/$USER/Mail/?

I've only been using:
; (setq nnir-wais-database "/home/reader/.wais/mail1")
; (setq nnir-search-engine `wais)
in ~/.gnus when trying to work with wais.
Maybe part of my troubles.

This new documentation you've done is really well done, I hope it
turns out to be worth the work you put in.



  reply	other threads:[~2000-06-23 23:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-17 18:21 Harry Putnam
2000-06-18 19:27 ` Kai Großjohann
2000-06-18 20:31   ` Harry Putnam
2000-06-18 22:25     ` Kai Großjohann
2000-06-19  0:18       ` Harry Putnam
2000-06-20 11:29   ` Harry Putnam
2000-06-20 16:30     ` Kai Großjohann
2000-06-20 23:32       ` Harry Putnam
2000-06-23 12:33         ` Kai Großjohann
2000-06-23 23:50           ` Harry Putnam [this message]
2000-06-24 19:36             ` Kai Großjohann
2000-06-24 23:23               ` Harry Putnam
2000-06-25  7:22               ` Norbert Koch
2000-07-19  4:11           ` Harry Putnam

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=m2r99o5540.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).