Well, um... It just does. Go on: type paren into the search box, and watch things go wrong. Doesn't seem to matter whether it's in quotes or not. This might be expected behaviour to some people, but wasn't to me.
Just thought somebody ought to know.
Oh, and previewing this comment seems to have destroyed it's title. (So I put it back...)

Replies are listed 'Best First'.
Breaking The Search Facility - And Repairing it
by stefan k (Curate) on Sep 17, 2001 at 14:25 UTC
    This could be a funny posting: I assume that _before_ you posted a node with the word 'paren' in it, actually something weird happened. Well, since you posted your node it just shows up in the list of found nodes. Maybe the title of your node should be changed, not to contain the buzzword, so we can see what goes wrong again?

    Regards... Stefan
    you begin bashing the string with a +42 regexp of confusion

      Thank you for the assuming that the behaviour has changed, rather than the fact that I've got things wrong. You're right: it has changed. Wierd!
      From work, I got a popup saying "Connection to www.perlmonks.org broken". From home, last night, I got a web page back, but it contained the text "Connection to server lost" (or similar).
      Wierdly, I got the same result last night with parenthesis, but now I just get thrown back to the gates.
      I'd be happy to change the title, but I don't know how, I'm afraid... Poor little newbie ;)

        Ok, I've got back to my home machine, since I was puzzled by the different behaviour I got in work.

        Home: Lynx 2.8.5 or Konqueror 2.2.1 on Mandrake
        Work: Konqy 2.2.1 on Solaris (from source)

        Searching on "pare" or "parenthesis" from home, using lynx gives me a "502 Server Hangup" warning. This is then followed by a mostly empty page:

                                         Server Hangup
             _________________________________________________________________
        
           Description: Server Hangup
             _________________________________________________________________
        
        With Konqy, I don't get the inital warning, just the error page.

        I've also tried it with "flibble", and get the same results. So I now suspect that there's a bug in the "zero hits" handler of the search engine (which explains why the problem on "paren" went away as soon as I reported it. Typical ;-)

Re: "paren" breaks search facility
by blakem (Monsignor) on Sep 17, 2001 at 22:19 UTC
    There appears to be a recent bug in the site such that any unknown 'node' value will simply close the connection. ala http://www.perlmonks.com/index.pl?node=aabasdfsdf. Since the search functionality is closely related to this, I'm guessing that they are two sides of the same coin.

    -Blake

Re: "paren" breaks search facility
by cLive ;-) (Prior) on Sep 17, 2001 at 14:54 UTC
    re.cur'sive - adj, see recursive.

    cLive ;-)

    ps - only kidding - see above - search for 'pare' and you get an empty doc - tim?

Re: "paren" breaks search facility
by Zoogie (Curate) on Sep 17, 2001 at 21:03 UTC
    I noticed the same problem, not with "paren", but with "commify" a couple days ago, and it still seems broken. Odd.

    - Zoogie