Author Topic: No files were found to look in with find in files search  (Read 6357 times)

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
No files were found to look in with find in files search
« on: August 24, 2020, 03:57:58 PM »
I've hit this issue a few times but so far have not been able to reproduce it with a small project.

I do a "Find in files" search. I know the search term is in one of the files, but SlickEdit states "No files were found to look in.". But there are files to look in. If I simply change the search term to something else (without changing "Look in:" or "File types") that I know is there it is found. It depends on the search term. After some time it doesn't reproduce.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Re: No files were found to look in with find in files search
« Reply #1 on: August 24, 2020, 04:09:08 PM »
What is lookin set to?

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: No files were found to look in with find in files search
« Reply #2 on: August 24, 2020, 04:10:31 PM »
lookin is set to a directory

File Types is set to:

CMakeLists.txt;*.cmake

I'm trying to construct a small project that reproduces it again.

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: No files were found to look in with find in files search
« Reply #3 on: August 24, 2020, 04:20:40 PM »
I tried making a smaller project with just the files to search, used a clean config, then tried clean config + my user.cfg.xml, can't reproduce it :(

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: No files were found to look in with find in files search
« Reply #4 on: August 24, 2020, 04:24:17 PM »
And it just stopped happening with my real project and my main SE installation. This issue has occurred for me a few times in past week or so.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Re: No files were found to look in with find in files search
« Reply #5 on: August 24, 2020, 04:31:05 PM »
Is the directory remote? Just wondering if the directory went off line.

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: No files were found to look in with find in files search
« Reply #6 on: August 24, 2020, 04:35:05 PM »
Directory is remote but I know for sure it is not offline.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Re: No files were found to look in with find in files search
« Reply #7 on: August 24, 2020, 04:40:14 PM »
Next time it happens, you could try switching to the Files tab and see if it lists any files.

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: No files were found to look in with find in files search
« Reply #8 on: September 13, 2020, 06:55:35 PM »
Its happening again now. I switched to Files tab and it is showing the found files. But with "Find in Files" it is saying "No files were found to look in".

I've seen this in both Linux and Windows with beta3. Don't know how to reliably reproduce it. Any hints?

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: No files were found to look in with find in files search
« Reply #9 on: September 13, 2020, 07:03:29 PM »
Some symptoms of the issue.

I have a directory with many scripts and 3 of the scripts have the string: "sshvarskeep.sh".

If I search for "sshv" it indicates 197 files searched and 3 files found.

If I add 1 character, "sshva", it indicates 97 files searched (100 less) and nothing found.

Add 1 additional character, "sshvar", and it says that no files were found to look in. Maybe it subtracted another 100 files and with -3 files it thinks there is nothing to search?

Anything special about subtracting 100?

There is another string that I searched in this directory before which was previously found. But now that I'm in some state where this problem is happening, it isn't finding it anymore. So not sure I can find a way to systematically repro it.

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: No files were found to look in with find in files search
« Reply #10 on: September 13, 2020, 07:09:26 PM »
And now it doesn't repro anymore, and all I did was some more normal usage, editing and searching.

I suspect there is some kind of memory corruption. Maybe the search string is overwriting some variables and that is why shorter search string didn't cause an issue while a larger one did.

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: No files were found to look in with find in files search
« Reply #11 on: September 16, 2020, 01:35:55 AM »
Happening again now. When I search "connect" it searches 451 files. When I add a space and search "connect ", which I know it should find, it states "no files were found to look in". Using "Files" tab it finds 454 files. So Files tab is finding 3 more files than "connect" which searches 451 files.

Perhaps the issue could be reproduced if try a "Find in Files" with a very long search string, then maybe it would cause whatever memory corruption may be occurring?

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Re: No files were found to look in with find in files search
« Reply #12 on: September 16, 2020, 02:42:40 AM »
Are you using the "List current context" check box? If you uncheck it, does the number of files change?

rowbearto

  • Senior Community Member
  • Posts: 2335
  • Hero Points: 132
Re: No files were found to look in with find in files search
« Reply #13 on: September 16, 2020, 02:46:41 AM »
I am using "List current context". When I uncheck it then it has 453 files instead of 451.

Some things changed since last post. In the last post "connect" found 451 files instead of 454. But when I do it again now, "connect" found all 454 files. So I changed the search string by repeating "connect " many times with pasting.

After I did that, and with "List current context" checked, it found 451 files. When I uncheck it, it found 453 files. Going back and forth was consistent, 451/453, when in both cases it should be 454.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6826
  • Hero Points: 526
Re: No files were found to look in with find in files search
« Reply #14 on: September 16, 2020, 03:03:55 AM »
Are you doing the search on Windows or Unix?

Are you specifying any excludes? If so, you could try removing that.