In addition to this current feature, I suggest to add the ability to set the depth levet separately for each dir directly in "Search in:" field to make a depth level for certain dirs there even lower or higher than global one set in "Search in subdirectories".
My ideas is to set the number of such depth levels with an backslash with following asterisk. Example:
Code: Select all
c:\dir1;c:\dir2\*;c:\dir3\*\*;c:\dir3\*\*\*
For c:\dir2\* the depth level is current directory (dir2 itself).
For c:\dir3\*\* and c:\dir3\*\*\* the depth levels are 1 and 2 respectively.
Backslash+asterinsk can also be threated as a depth level marker for paths to search in of the text file list (which path in "Search in:" should start with at-sign (@, e.g. @c:\list.txt).)
Note 1. The asterisks (*) and question mark (?) usually are used as wildcards in context of a search, but in "Search in:" field of Total Commander these characters currently not supported as wildcards, or for any other meaning.
But if they will be supported here, it shouldn't harm the suggestion above because only backslash+asterinsk with no characters in between should be treated as a marker of depth level.
For example,
Code: Select all
c:\t*cmd*\*
So it would find e.g. c:\totalcmd\Plugins but not c:\totalcmd\Plugins\WCX.
Note 2. Regarding backward compatibility.
Current (then-older) Total Commander version usually will skips the paths containing more than 2 asterisks, although not silently - error messages will be shown like this one:
Code: Select all
---------------------------
Total Commander
---------------------------
Search path not found!
c:\*\*
---------------------------
OK
---------------------------
Anyway, the searches with asterisks saved as templates in Load/Save Find Files' tab shouldn't really break anything for older TC versions using the same wincmd.ini file.