From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/31447 Path: main.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: example queries for nnir Date: Sat, 17 Jun 2000 11:21:13 -0700 Sender: owner-ding@hpc.uh.edu Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035167855 14071 80.91.224.250 (21 Oct 2002 02:37:35 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:37:35 +0000 (UTC) Cc: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?UNKNOWN?Q?Gro=DFjohann?=) Return-Path: Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1]) by mailhost.sclp.com (Postfix) with ESMTP id EA87AD0520 for ; Sat, 17 Jun 2000 15:16:38 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id OAC11863; Sat, 17 Jun 2000 14:13:02 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sat, 17 Jun 2000 14:11:27 -0500 (CDT) Original-Received: from Post-Office.UH.EDU (Post-Office.UH.EDU [129.7.1.20]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id OAA01183 for ; Sat, 17 Jun 2000 14:10:27 -0500 (CDT) Original-Received: from CONVERSION-DAEMON by Post-Office.UH.EDU (PMDF V5.2-32 #40812) id <0FWB00H019PQIF@Post-Office.UH.EDU> for ding@hpc.uh.edu; Sat, 17 Jun 2000 13:22:38 -0500 (CDT) Original-Received: from mailhost.sclp.com (sclp3.sclp.com [204.252.123.139]) by Post-Office.UH.EDU (PMDF V5.2-32 #40812) with ESMTP id <0FWB00GP99PPTJ@Post-Office.UH.EDU> for ding@hpc.uh.edu; Sat, 17 Jun 2000 13:22:38 -0500 (CDT) Original-Received: from mail.networkone.net (mail.networkone.net [209.144.112.75]) by mailhost.sclp.com (Postfix) with SMTP id 3B25DD051F for ; Sat, 17 Jun 2000 14:21:21 -0400 (EDT) Original-Received: (qmail 28546 invoked from network); Sat, 17 Jun 2000 18:21:20 +0000 Original-Received: from adsl-117-113.ln.networkone.net (HELO reader.ptw.com) (209.144.117.113) by mail.networkone.net with SMTP; Sat, 17 Jun 2000 18:21:20 +0000 Original-Received: (from reader@localhost) by reader.ptw.com (8.9.3/8.9.3) id LAA05652; Sat, 17 Jun 2000 11:21:17 -0700 Original-To: ding@gnus.org User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.5 Original-Lines: 48 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:31447 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:31447 A small request for nnir users with some experience, to post a few sample queries using the `glimpse' or `wais' engines. Very unfamiliar with wais here, so any examples would be very usefull. Glimpse queries can be difficult since glimpse doesn't allow full regexp in the actual query string. This can make something like searching for a subject where you don't know the full string difficult since ^Subject:.*KEYWORDS won't work. In fact even when you do know the subject line in toto the glimpse syntax in nnir usage can be elusive. Maybe, if some nice generic broad usage examples showup someone (like me) will sort/edit them and submit a patch to Kai for possible inclusion in the nnir comments. Also some clear examples of how the nnir variables might be set would be a good inclusion in that document's comments. An example that can be confusing is(from nnir.el): ;; . . . . . . . . . . . . . . . . . . . . . . . . . . . . The ;; second variable to set is `nnir-search-engine'. Choose one of the ;; engines listed in `nnir-engines'. This is not really a list of engines at all but lisp code: nnir-engines's value is ((glimpse nnir-run-glimpse ((group . "Group spec: "))) (wais nnir-run-waissearch nil) (excite nnir-run-excite-search nil) (imap nnir-run-imap nil)) When the needed variable setting for glimpse is: (setq nnir-search-engine `glimpse) Not immediately apparent what is needed unless you know lisp. Showing some example settings would be a little less confusing. A final query.. Does anyone know of a search tool that uses a database but also allows full regexp use in the queries? This seems to be mutually exclusive, or something.