Content Indexing Suggestions

Discussion related to "Everything" 1.5 Alpha.
Post Reply
defza
Posts: 30
Joined: Thu Apr 18, 2019 12:49 pm

Content Indexing Suggestions

Post by defza »

Would like to see how many files are being searched? e.g. 23/2345 ?
Also, how about being able to see what file is currently being searched? e.g. Tools -> Debug -> Show current operation details....

I would like to get an idea of how efficient my regex:content: search is, by guaging how it takes to search files and get through the results.
void
Developer
Posts: 16508
Joined: Fri Oct 16, 2009 11:31 pm

Re: Content Indexing Suggestions

Post by void »

I like to gauge the number of results before typing in my content: search.

I will consider showing the total number of files searched for content in the status bar.


Content search progress is shown in the status bar on the right.
I will consider showing the current content search filename in the tooltip of the progress bar.

There is some timing information shown in the debug console (Tools -> Debug -> Console)
content match cache 2.012043 seconds

Thank you for the suggestions.
defza
Posts: 30
Joined: Thu Apr 18, 2019 12:49 pm

Re: Content Indexing Suggestions

Post by defza »

Content match cache:

How do I do a content search without the cache? e.g. force the query to do a raw content search from scratch?
Or to try and repopulate any attribute without using the cache values?
void
Developer
Posts: 16508
Joined: Fri Oct 16, 2009 11:31 pm

Re: Content Indexing Suggestions

Post by void »

How do I do a content search without the cache?
The 'content match cache' only lasts for the active search.
As soon as the search changes, all 'content match cache' is cleared.

The 'content match cache' only records the filename and if the content search matched. (there's no content cache)



Hit F5 to clear property cache.
void
Developer
Posts: 16508
Joined: Fri Oct 16, 2009 11:31 pm

Re: Content Indexing Suggestions

Post by void »

Everything 1.5.0.1310a improves content match cache.

Everything will no longer discard content match cache when a file changes.
Instead, Everything will keep the old content match cache and perform a new content match in the background.

Everything should now no longer 'flicker' changing results.
Post Reply