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

rowbearto

  • Senior Community Member
  • Posts: 1974
  • Hero Points: 122
Re: No files were found to look in with find in files search
« Reply #30 on: September 16, 2020, 04:23:44 pm »
OK. Even so the 2 files that the diff of 10.txt and 11.txt show are not binary files, they are text files. I can upload them to support if you like. And I don't think that I have any binary files in this directory that I'm searching.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5950
  • Hero Points: 467
Re: No files were found to look in with find in files search
« Reply #31 on: September 16, 2020, 04:35:07 pm »
I don't think you're following what I'm saying.  I found a couple bugs. The bugs that I found do not explain the problems you are having. They are bugs having to do with the "Total files searched" count being wrong because binary files (typically files with no extension) are being included in the "Total files searched" count. If you have files with no extension that are binary, this will help confuse what's going on here. The "Total files searched" count is currently only correct for a multi-file search which does not have the "List current context" checked. The Files tab is incorrect as well for binary files with no extension.
« Last Edit: September 16, 2020, 05:42:38 pm by Clark »

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5950
  • Hero Points: 467
Re: No files were found to look in with find in files search
« Reply #32 on: September 17, 2020, 09:59:31 pm »
Found and fixed the major problem where results are random and may find NO FILES when the "List current context" option is used.

Fixed for beta 4

rowbearto

  • Senior Community Member
  • Posts: 1974
  • Hero Points: 122
Re: No files were found to look in with find in files search
« Reply #33 on: September 18, 2020, 02:30:10 am »
Excellent! That's amazing! Thanks Clark. Look forward to getting it, hopefully you nailed it!

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5950
  • Hero Points: 467
Re: No files were found to look in with find in files search
« Reply #34 on: September 18, 2020, 01:59:22 pm »
Give beta 4 a try. Should be much better.

rowbearto

  • Senior Community Member
  • Posts: 1974
  • Hero Points: 122
Re: No files were found to look in with find in files search
« Reply #35 on: September 23, 2020, 04:08:37 pm »
Using beta4 now on Windows.

I'm trying to search all files in a directory, but it just hangs and doesn't show anything. When I stop the search with the Stop button in Find in Files, it says "Search terminated" and "No files were found to look in".

The "Files" tab is also hanging.

This is in a subdirectory of c:\Program Files(x86), not sure if that makes a difference.

I removed all excludes and unchecked "List current context", still get the hang. I can also stop the "Files" tab and it gives same message as when I stop the "Find in Files" tab.

rowbearto

  • Senior Community Member
  • Posts: 1974
  • Hero Points: 122
Re: No files were found to look in with find in files search
« Reply #36 on: September 23, 2020, 04:11:45 pm »
I closed and restarted SlickEdit, the issue went away.

Before closing I tried a directory I own just under c: and it was hanging there too.

After restart no hang in either my dir or the Program Files(x86)

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5950
  • Hero Points: 467
Re: No files were found to look in with find in files search
« Reply #37 on: September 23, 2020, 06:00:47 pm »
Load this debug version of bgsearch.e.

This will dump almost all the parameters passed to the background process (sgrep or vs) to vs.log. When you get a problem, you can take a look at vs.log and post it here.

The previous issue you had was a problem where excludes were getting truncated. This log will let us know exactly what is getting passed to the the search process.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5950
  • Hero Points: 467
Re: No files were found to look in with find in files search
« Reply #38 on: September 24, 2020, 03:12:39 am »
Do you have "Sort Find in files search results by filename" turned on?  (Tools>Options>Editing>Search).

If you have this on, I recommend you turn it off. When this option is on, it drastically slows down how long it will take before you see any feed back from SlickEdit.

v25 has better output when this option is turned off. v25 outputs the filenames in the order the file system orders the files which is fairly sorted. Prior versions did not do this.

rowbearto

  • Senior Community Member
  • Posts: 1974
  • Hero Points: 122
Re: No files were found to look in with find in files search
« Reply #39 on: September 24, 2020, 03:47:35 pm »
I have never enabled "Sort Find in files search results by filename" and I checked that it is OFF in my config. So when I saw this issue that was OFF.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5950
  • Hero Points: 467
Re: No files were found to look in with find in files search
« Reply #40 on: September 24, 2020, 04:31:32 pm »
I just wanted to rule that out. Just run with that debug version of bgsearch.e. Hopefully, it will help us figure this out.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5950
  • Hero Points: 467
Re: No files were found to look in with find in files search
« Reply #41 on: September 25, 2020, 07:06:41 am »
RC 1 has the same logging output but it's off by default. To turn it on, set the macro variable def_mfdebug to 1

rowbearto

  • Senior Community Member
  • Posts: 1974
  • Hero Points: 122
Re: No files were found to look in with find in files search
« Reply #42 on: September 25, 2020, 01:13:03 pm »
Would it be possible that I only enable this if/when the issue starts occurring again?

I'd rather not have it enabled all the time and forget that it is on.

So far I haven't had this issue repeat yet, but I think it may have happened on 2 different occasions.

I have RC1 now in Linux. Will change in Windows soon when I start using it.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5950
  • Hero Points: 467
Re: No files were found to look in with find in files search
« Reply #43 on: September 25, 2020, 01:25:20 pm »
You don't need to have it on all the time. It's up to you. Should not effect performance. vs.log will keep growing but quite slowly.