Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org,
	"Norbert Gövert" <goevert@amaunet.cs.uni-dortmund.de>,
	"Ulrich Pfeifer" <upf@de.uu.net>
Subject: Re: nnir/freeWAIS-sf
Date: Thu, 20 Jul 2000 16:48:48 +0200	[thread overview]
Message-ID: <vafk8egrh67.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Harry Putnam's message of "15 Jul 2000 06:53:03 -0700"

On 15 Jul 2000, Harry Putnam wrote:

> 2) Queries aimed at `from' or `to' fields fail, although queries to
>    `subject' field or global queries, work

I have now, finally, found the solution.  Stupid me :-/

It seems formulating fwsf queries isn't as simple as I thought it
would be...

waissearch -d ~/.wais/mail 'from=(soundex zeimetz)'

This is the magic incantation.  Okay.  So, if you choose `SOUNDEX LOCAL
TEXT BOTH' for a field, then you can do the following:

waissearch -d ~/.wais/mail 'from=(soundex zeimetz)'
    This searches for similar-sounding names.

waissearch -d ~/.wais/mail 'from=zeimetz'
    This applies the normal term-search routines.

Does it now work for you use fmt specs like the following:

region: /^([tT][oO]|[cC][cC]):/ /^([tT][oO]|[cC][cC]): */
        to "To and Cc headers" SOUNDEX LOCAL TEXT BOTH
end: /^[^ \t]/                          

This way, you should be able to find names by saying `to=(soundex
NAME)' in the query.

kai
-- 
I like BOTH kinds of music.



  parent reply	other threads:[~2000-07-20 14:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-15 13:53 nnir/freeWAIS-sf Harry Putnam
2000-07-15 18:04 ` nnir/freeWAIS-sf Norman Walsh
2000-07-15 18:10 ` nnir/freeWAIS-sf Francisco Solsona
2000-07-15 21:22   ` nnir/freeWAIS-sf Harry Putnam
2000-07-17 13:51     ` nnir/freeWAIS-sf Francisco Solsona
2000-07-18  1:03       ` nnir/freeWAIS-sf Harry Putnam
2000-07-18  9:06         ` nnir/freeWAIS-sf Kai Großjohann
2000-07-19  0:57           ` nnir/freeWAIS-sf Harry Putnam
2000-07-20 14:34             ` nnir/freeWAIS-sf Kai Großjohann
2000-07-20 18:13               ` nnir/freeWAIS-sf Harry Putnam
2000-07-21 17:31                 ` nnir/freeWAIS-sf Kai Großjohann
2000-07-21 22:35                   ` nnir/freeWAIS-sf Harry Putnam
2000-07-16 12:25 ` nnir/freeWAIS-sf Kai Großjohann
2000-07-16 16:17   ` nnir/freeWAIS-sf Harry Putnam
2000-07-16 21:43     ` nnir/freeWAIS-sf Kai Großjohann
2000-07-16 22:22       ` nnir/freeWAIS-sf Harry Putnam
2000-07-20 14:44         ` nnir/freeWAIS-sf Kai Großjohann
2000-07-16 23:08       ` nnir/freeWAIS-sf Harry Putnam
2000-07-20 14:48 ` Kai Großjohann [this message]
2000-07-20 16:33   ` nnir/freeWAIS-sf Harry Putnam
2000-07-21 17:27     ` nnir/freeWAIS-sf Kai Großjohann
2000-07-21 22:04       ` nnir/freeWAIS-sf Harry Putnam
2000-07-21 22:34         ` nnir/freeWAIS-sf Kai Großjohann
2000-07-21 23:12           ` nnir/freeWAIS-sf Harry Putnam
2000-07-22 11:59             ` nnir/freeWAIS-sf Kai Großjohann
2000-07-22 13:40               ` nnir/freeWAIS-sf 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=vafk8egrh67.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    --cc=goevert@amaunet.cs.uni-dortmund.de \
    --cc=upf@de.uu.net \
    /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).