BUG: Supersearch won't search more if first search is empty

I was doing a supersearch on "cpan://types" and the first 25% of the database was searches and nothing was found. So, I clicked on "keep searching" and it searched the same 25% of the database.

My wife's blog

Comment on BUG: Supersearch won't search more if first search is empty

Replies are listed 'Best First'.
Re: BUG: Supersearch won't search more if first search is empty (1 found) by tye (Sage) on Apr 12, 2005 at 20:03 UTC
I noticed a similar bug just recently. The case I saw was it searched 93% of the database and only found one hit near the 1% mark. It started the next search right after that hit even though it had already searched 92% of the database after that. But since the second batch found no hits, the bug didn't recur and the third time it just searched the small remainder of the database. Perhaps you saw this case rather than what you reported (since holli and I haven't been able to reproduce it)? But I'll look for cases that don't set the point to search next correctly besides the one I recently identified but haven't had a chance to fix yet. - tye	[reply]
Re: BUG: Supersearch won't search more if first search is empty by holli (Abbot) on Apr 12, 2005 at 19:40 UTC
Searching for "cpan://types" naturally now returns some hits. But I super-searched for "uhfsdfsafgdzgfuzkgf" and pressed "Next >" multiple times. It worked as expected. holli, /regexed monk/	[reply]