Page 1 of 1

BUG: Normal Find misses most occurrences

Posted: 2006-09-20 10:23:49
by Bob Stern
I discovered that Normal Find works correctly if I use the Find All or Replace All buttons, but misses most occurrences of the search string if I use Next or command-G.

PowerFind does not have this problem.

This has happened in several documents. The current document is 6300 words or 40,000 characters.

I also reported this bug directly to Nisus using "Send Feedback", but I wanted to warn the user community because you could really mess up a document if you're not aware of this.

Posted: 2006-09-20 12:40:13
by ssampler
Thanks, Bob.

I also found that Normal "Find Next" does not work--sometimes misses occurrences of the word and occasionally alternates back and forth between two occurrences.

This happens whether or not "Whole Word" " and "Ignore Case" are checked.

OS X 10.4.7 PB G4


Posted: 2006-09-20 13:13:13
by martin
I received the feedback report you sent in Bob. Is there any chance either of you could send me the file in which the problem occurs? It would also be very helpful to know what exactly you are searching for. Thanks for your help Bob & Steve.

sample document

Posted: 2006-09-20 13:55:43
by Bob Stern
I would have attached the document to the feedback report, but it is confidential. Tonight I'll look for a non-confidential example.

I'll assume submitting another feedback report is the best way to forward the example document unless you instruct me otherwise.

Posted: 2006-09-20 13:59:10
by Bob Stern
Martin, in response to the last part of your question, my last two searches in which the bug appeared were searches for "13" and "Hz". The scope was Entire File, and both Whole Word and Case Sensitive were turned off.

Posted: 2006-09-21 15:49:56
by Bob Stern
PLIST file was the culprit!

I discovered the problem occurred on only one of my two computers. I copied the Nisus plist file from the good computer to the bad one, and the problem disappeared.

Martin, do you want me to send you my good and bad plist files so you can figure out what went wrong, or should we forget it unless the problem recurs?

It is worrisome that one other member of this forum has the same problem.

Posted: 2006-09-22 07:26:21
by ssampler
Deleting the plist worked for me, too. Thanks, Bob!