Indexing Feedback

[Maseron]

Quick feedback on useful Pause Updating: if you delete a file via Everything with Pause Updating enabled, the file remains listed. I'm not 100% sure of all the intended uses for Pause Updating, but it would probably make sense either to remove the file from the listing or better yet to highlight the deleted file in a different color like gray or dark red.

Some obvious issues with this: There are two types of deletes, via the DEL keyboard shortcut and via the context menu. I'm sure Everything can keep track of keyboard deletions, but I don't know enough about Windows programming to know if it's even capable of interfacing with the context menu after summoning it and "understanding" that a Delete command has been executed. The same goes for keeping track of renames.

[void]

Everything 1.5 has a nonewresults: search function.

Please consider creating a search filter to prevent Everything from adding new results:

• In Everything, from the Search menu, click Add to filters....
• Change the Name to: No New Results
• Change the Search to: nonewresults:
• Click OK.

Filters can be activated from the Search menu, Filter bar (View -> Filters), right clicking the status bar, filter macro or filter keyboard shortcut.


Technically Everything doesn't know you delete a file from within Everything.
Deletion is handled by the Windows Shell.



One reason for Pausing/stopping updates is to release any volume handles Everything may have open.
Another is for opening the database as read-only.



I will look into an option to allow delete from within Everything to always remove results (even when paused).
Thank you for the suggestion.

[meteorquake]

That has some useful comments there.
Is there an equivalent of nonewresults that applies to sorting, so the sorting is fixed but new items can still appear (unless nonewresults), they just get added at the end?
Ever since windows was changed from XP, I have found file management a daily nightmare caused by being unable to turn on/off live sorting.
d

[NotNull]

One reason for Pausing/stopping updates is to release any volume handles Everything may have open.
Another is for opening the database as read-only.

Pause Updates is very useful in debug mode. It filters all disk activity from the log, creating cleaner output.
(that is what I use it for, at least)

[void]

I will consider an option to add new results to the end of the list.

Thank you for your suggestion.

For now, please consider sorting by Date Recently Changed.
New results and changed results (including renamed files) will appear at the top of the list.