Find dialog bug?

jeffy · Post by **jeffy** » Sat Jul 27, 2013 7:23 pm

Try this:

Type '\' (no quotes) into the find-dialog. Click regular expression. It's an invalid regex, because it's an unescaped escape character. Click find-next and you'll get an error.

Now, leave the slash there and close the dialog. Select some text (within a single line), and re-open the dialog. The selected text--I thought--should be put into the find-what field, and--I thought--the regex checkbox should be cleared.

But instead, it gives you a regex error, because the *SLASH* is a bad regex.

Is this a bug? Are other people seeing this?

Post by **MudGuard** » Sun Jul 28, 2013 8:37 am

can't reproduce. If selected text is within a single line, the find field is filled with the selected text.
If selected text crosses a line break, the find field is filled with the last (valid) find expression.

jeffy · Post by **jeffy** » Sun Jul 28, 2013 4:52 pm

Happens consistently with me. Including after a computer-restart.

No one else?

kengrubb · Post by **kengrubb** » Wed Jul 31, 2013 4:35 pm

What version of TP are you running?

jeffy · Post by **jeffy** » Wed Jul 31, 2013 5:35 pm

7.0.8.

I just upgraded to 7.0.9 and it still happens.

kengrubb · Post by **kengrubb** » Thu Aug 01, 2013 12:10 am

I don't recall a version 7.0.8

Can you do a Help, About to confirm that 7.0.9 is installed?

I know there were some RE issues with unmatched and/or invalid RE, but I believe those all have been fixed with 7.0.9

I am unable to reproduce the problem.

Win7 64 bit
TP 7.0.9

jeffy · Post by **jeffy** » Thu Aug 01, 2013 2:17 am

7.0.8 was privately given to me and some others who were experiencing a specific problem.

What I said is correct. It happened in 7.0.8, and is WAS happening in 7.0.9...consistently up until right now. I can't reproduce it at the moment, which is the first time that it's NOT happening. I'll try it again tomorrow...

jeffy · Post by **jeffy** » Thu Aug 01, 2013 11:47 am

Still happening after a computer restart, in 7.0.9.

kengrubb · Post by **kengrubb** » Thu Aug 01, 2013 9:20 pm

I'm wondering whether this could be an upgrade problem with 7.0.8 to 7.0.9

Not sure if this would work, but you might try installing 7.0.7, and then upgrading from 7.0.7 to 7.0.9

jeffy · Post by **jeffy** » Tue Aug 13, 2013 11:07 am

Honestly, I've not yet tried the uninstall-reinstall-upgrade as you suggested. However, I did find a related problem.

When you're outside of the find dialog and trigger the "RegexSet" command, then you open the find dialog; if there happens to be a bogus regex command in it, you get the modal regex-is-bad dialog.

In my opinion, this error message should never appear just because you opened the find dialog (with RE checked). Rather, the regex should only be analyzed when pressing the find-next button.

Please tell me I'm not the only one having this problem!