Author Topic: find_next fail  (Read 1145 times)


  • Senior Community Member
  • Posts: 2115
  • Hero Points: 189
  • Text
find_next fail
« on: September 01, 2017, 06:37:44 pm »
find_next seems to get out of sync with the find options - in particular color coding.
I don't have repro steps, but basically I used big-find dialog to search for "blah", color coding: NotString,NotComment.

I hit FIND, and its good.
I hit F3, and the next thing it finds is "blah" as a string -- ignoring the color coding option.

As I tried to repro for writing this report, I've got the opposite problem - I've cleared the color coding options but they still seem to be being enforced by find_next.

I don't know if it matters, but I'm searching in a *.py file.


  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5553
  • Hero Points: 449
Re: find_next fail
« Reply #1 on: September 01, 2017, 11:13:31 pm »
No luck reproducing this. Keep in mind that displaying the big-find dialog and changing color coding options has no effect until you do another find (press Find button). At least that's the way its supposed to work.