Newsgroups: comp.sys.next
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!atrans.engin.umich.edu!dejnsen
From: dejnsen@caen.engin.umich.edu (Nik Anthony Gervae)
Subject: Re: Shakespeare and Librarian: annoying little bug
Message-ID: <1991Apr26.032102.10138@engin.umich.edu>
Sender: news@engin.umich.edu (CAEN Netnews)
Organization: University of Michigan Engineering, Ann Arbor
References: <5098@lectroid.sw.stratus.com> <7410001@hpfcso.FC.HP.COM>
Date: Fri, 26 Apr 1991 03:21:02 GMT

In article <7410001@hpfcso.FC.HP.COM> chance@hpfcso.FC.HP.COM (Chance Brohm) writes:
>(**DRIFT WARNING**)
>
>Another weird problem I noticed last night WRT Shakespeare:  while expounding
>on the virtues of my new NeXTCube to some friends, I decided to look up the
>famous soliloquy from Hamlet, "To be, or not to be..."  Bad choice! I tried
>looking up just "not to be" (in case the punctuation was wrong) as well as
>neighboring phrases like "slings and arrows" and "outrageous fortune".
>All of these searches returned (after a LONNNG pause) with "0 Found" - WHY?
>
>Being not intimately familiar with Hamlet, I'm not sure which Act/Scene
>this appears in, but my quick glances through the individual files did not
>reveal this passage either.  In desperation (my friends were saying unkind
>things at this point...) I went to Quotations, and lo! there was exactly
>the passage I had been searching for.   :-|
>
>Later on (alone with my obstreperous cube) I completely re-indexed the
>Shakespeare target.  No help.  I also was displeased to notice on closer
>inspection that the citation in Quotations did not include the Act/Scene
>number, but rather only a line number (wow - that's useful!).  :-(
>
>I'm certainly willing to believe that it's entirely pilot error - please
>tell me where I missed the mark. (Also, if you know the Act/Scene/Line of
>that soliloquy, I'd appreciate knowing that too).
>
>Thanks!
> -Chance
  It's sort of a pilot error. One thing you must keep in mind is that indexing
throws out short words (like "to", "be", "not", "or"...sound familiar?). So,
if you're gonna look for this phrase (or *any* phrase--see below), TURN
USE INDEXES OFF first. And yes, it'll take a while; and yes, mind your
puntuation (and probably capitalization too).

  Another thing is that in use indexes mode, Librarian looks for any file
with all the specified words in it--they can be out of order or disjoint.
Librarian is more of a keyword-search tool than a true text searching
tool. If you know the phrase is in Hamlet, for example, you can click on 
"Stop" as soon as you see that title disappear in the searching field....
(just an example).

  Hope that helps.

  [Patient: doctor, when I bend over it hurts.
   Doctor:  So don't bend over. ]

   ;-)


--
/ Nik Gervae aka dejnsen@caen.engin.umich.edu | "It'll be finished next week, \
| CS/Linguistics stud. & NeRD at UM (go blow) | I promise!"--me               |
|                                             |                               |
| **When all else fails, bug someone who      | "Just say an iguana chewed    |
\   knows (not me!).                          | up your textbook."--Jason Fox /
