From: Harry Putnam <reader@newsguy.com>
Subject: Re: example queries for nnir
Date: 18 Jun 2000 13:31:43 -0700 [thread overview]
Message-ID: <m2ya42k9xs.fsf@reader.ptw.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sun, 18 Jun 2000 21:27:28 +0200"
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
^^^^^8< snipped good clues and examples about freeWAIS
> It doesn't? The documentation seems to say it should. Does
> `^Subject:#KEYWORD' do anything useful?
>
> Oh, now I see that the documentation doesn't mention `^', so that's
> why it doesn't work. But does `Subject:#KEYWORD' work?
>
> `#' seems to be an abbrev for `.*'.
You've neatly summed up the reason I say it is difficult.
Trying: C-u G G <RET>
Query: 'Subject:#queries'
or
Query: Subject:#queries
Either way produces:
Invalid read syntax: "#"
Query: Subject:.*queries
Invalid read syntax: "."
Even:
Query: ^Subject: example queries for nnir
or
Query: Subject: example queries for nnir
with and without single quotes
Wrong type argument: listp, example
Trying to use the ";" operator (even though it would leave a gaping
whole for false hits):
Query: Subject:;queries
End of file during parsing
All the above leave room for false hits without the "^".
I think this points up the weakness I mentioned. And a good reason
why it would be nice if RE were usable in the queries of glimpse.
It appears that freeWAIS get around this problem neatly by use of
`fields' as you've described.
next prev parent reply other threads:[~2000-06-18 20:31 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 [this message]
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
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=m2ya42k9xs.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).