voidtools forum

1. Rename Exclude to Exclude/IncludeOnly or something else, that says it's also for "IncludeOnly".
2. Move "include only" from NTFS/ReFS and put it in Exclude/Include tab.
3. To use the same syntax of the SearchBox, for 'Exclude'/'Include only'. It will be easier to non-beginner users.

You can also add this filter to INDEXES tab

indexes filter:
______________________________________
______________________________________|

The user will type in:

"c:\window"
to include only "c:\window" folder.
"c:\window"|"e:\Everything".
to include only "c:\window" and "e:\Everything" folders .

or
!"c:\windows"
to exclude "c:\windows".

!folder:"*.metadata"
!folder:regex:\.metadata\Z

For users that have many drives, including only c:\windows on the C: drive would be a pain to type out:
c:\windows|d:|e:|f:|g:|h:|i:|j:|t:

The include only option should be on a per drive basis.
However, this could be moved to the Exclude tab to keep all these exclude options in one place.

Everything 1.2 did have some more advanced filters. These were removed in favor of something more user friendly.
I'll consider adding an advanced filter option back.

Also on my TODO list is the context menu option to exclude files already indexed, this could be extended to exclude *this* file extension, *this* file parent folder, *this* file etc...

Although, indexing everything and asking questions later might not be the preferred method..

These are the type of things I'll be developing and testing for Everything 1.5.

Thanks for the suggestions.

For users that have many drives, including only c:\windows on the C: drive would be a pain to type out:
c:\windows|d:|e:|f:|g:|h:|i:|j:|t:

The "indexes filter" it's not instead of, but in addition.
The user needs to have the pain just once, and only in cases it will be easier than do it by the Folder browsing selection.

btw, hmm... am I right? (more expert than me will probably get the correct regex)

Also on my TODO list is the context menu option to exclude files already indexed, this could be extended to exclude *this* file extension, *this* file parent folder, *this* file etc...

I don't think that "context menu option to exclude files already indexed" is good thing to do.
Exclude via context menu is good just for the current session,
but not to exclude from DataBase. This thing should be via the options.

Another suggestion,
I think I mentioned once, this type of FolderTree or similar:

For users that have many drives, including only c:\windows on the C: drive would be a pain to type out:
c:\windows|d:|e:|f:|g:|h:|i:|j:|t:

Another try...
1. To include only "c:\windows" on the C: drive, I will try first to display in the results list all folders and files I want to be excluded later:
C:\ !"c:\windows"
(= all folder and files in C: drive excluding "c:\windows" folder)
Now I have in results list all folders and files I want to be excluded from index/database.
Therefore,
2. I need to exclude from index/database the search I wrote in step 1. (C:\ !"c:\windows"):
!"SEARCH"
!"C:\ !"c:\windows""
for some reason it didn't work.
But I tried:
!<SEARCH>
!<C:\ !"c:\windows">
and it did work

Now, only if I had a command...
Menu: File > Save Search as an Index/DataBase

void wrote:Although, indexing everything and asking questions later might not be the preferred method..

What's the difference between:

1.
Excluding folders
C:\Folder1
C:\Folder2
by "Add Folder..." button

and

2.
Exclude those folders by a search string:
!"C:\Folder1" !"C:\Folder2"

Can't we make 2. method to work like 1. method?