Main Area and Open Discussion > General Software Discussion
FolderSize o DirectorySize with rules or filters
rjbull:
It's like a two dimensional filter: the first axis is the folder dimension, the second axis is the files dimension. Both are perpendicular and not directly related.
[...]
Consider this example:
root
|
+Program Files
| |
| +Data
|
+Users
| |
| +Programs
| |
| +Data
|
+Windows
| |
| +System
The previous folder mask will consider all files under "Program Files\..." and all files under "Users\Programs\..." but not other branches because they don't contain "program*".
-uuderzo (January 13, 2011, 04:25 PM)
--- End quote ---
I didn't realise that the folder wildcard implied the equivalent of DOS wildcard "*folder*". I thought it meant "folder*", no front wildcard, so would only apply to the green branch above. It would have excluded everything else, shown in red branch. I just needed to grasp that it's *folder*. I think I see what you mean about having two dimensions of filters.
Suppose that your disk structure contains many folders with similar names, but you don't know how many and where they are (and at which nesting level they are). Without a folder mask you must examine each branch of the disk structure to find them. With folder mask you can find every "temp" folder with a click.
--- End quote ---
That problem is a real pain with my file manager, Total Commander. Anything to help is welcome!
uuderzo:
RJ,
I think that if one wanted to explore just folder*, he would start the snif operation from that folder instead of the entire drive. A folder* behavior wouldn't add in flexibility. It would be only a different mean to obtain the same result.
So, do you consider the current release candidate behavior useful?
Greetings! Umberto
rjbull:
I think that if one wanted to explore just folder*, he would start the snif operation from that folder instead of the entire drive.-uuderzo (January 14, 2011, 03:57 PM)
--- End quote ---
Yes. I'm not thinking clearly again. An all-to-frequent state of affairs :-[
So, do you consider the current release candidate behavior useful?
--- End quote ---
Yes, but, please can you make sure the folders and filters wildcards are explained in Help, like you did above?
uuderzo:
Sure.
Here it is an extract of the User Manual about the folder name filter:
"The filter by file name mask applies only to files. Sometimes you may want to search only under some folders, say, temp folders. You don't know where they are and at which nesting level on you media device, but you know they are there, and possibly more than one.
In this case you can use a folder name mask filter. Folder name mask filters are the same as file name mask filters, except they apply to folders. To identify a pattern as a folder mask pattern, simply prepend it by the '\' (backslash) char. The backslash char doesn't have the meaning of "root folder", it is simply a switch. It has been choosed as "switch" char because it is forbidden in file and folder names (it is a path separator), hence it cannot exist into an element name.
When you apply a folder name mask filter, only files whose path contains a matching folder are inluded. Moreover, folders which name matches the mask are hilighted with the BOLD style in their name. This makes easy to understand why stuff has been included by the filter. If, on the other hand, you are using an exclusion filter (by prepending the whole pattern string by the negation pipe (|) char), excluded folders are not hilighted just because they will not be displayed.
Example: by typing \temp every file under a temp folder (at any nesting level) is included. For example, C:\Windows\temp\data\abc.txt would be included.
Example: on the countrary, by typing |\temp every file under a temp folder (at any nesting level) is excluded.
Hint: You can consider folder and file masks as a two dimensional filter. The first axis is the folder mask, the second axis is the file mask. Both axis work independently. When you apply a folder+file mask you are defining some kind of "coordinate" in a 2D space. You first "cut" the directory tree structure and isolate the searched folders, then examine the wanted file names by the other mask."
...and, on the online quick tip window...
By folder name
Same as by file name, but prepend with '\' (backslash) (|).
The folder mask considers files whose path contains elements
that match the mask at any nesting level.
Matching folders are renderer with BOLD font.
The mask itself cannot include the '\' char.
Example: \temp will include only files whose path contain
at least a 'temp' folder.
For example, C:\windows\temp\data\abc.txt is ok
Example: |\progr* will exclude files whose path contain
at least a 'progr*' folder.
The starting backslash char does not mean 'the root', it has
been choosed as switch because it is a forbidden char
in files and folders name.
(Note: Folder masks are slower than file masks)
Honestly, i'm still looking for the "magic words" that make the user understand the concept with less text. Sometimes i've a bit of difficulty because i'm not english native. Hints are welcomed!
Greetings! Umberto
rjbull:
Honestly, i'm still looking for the "magic words" that make the user understand the concept with less text. Sometimes i've a bit of difficulty because i'm not english native. Hints are welcomed!-uuderzo (January 16, 2011, 03:35 PM)
--- End quote ---
I should warn you than whenever I've "helped" someone's "magic words," the author generally ends up thinking I make it too long! But I think that's excellent. I've taken the liberty of changing a few spellings and very minor grammar points, but what you meant is perfectly clear:
"The filter by file name mask applies only to files. Sometimes you may want to search only under certain folders, say, temp folders. You don't know where they are and at which nesting level on your media device, but you know they are there, and possibly more than one.
In this case you can use a folder name mask filter. Folder name mask filters are the same as file name mask filters, except they apply to folders. To identify a pattern as a folder mask pattern, simply prepend it by the '\' (backslash) char. The backslash char doesn't have the meaning of "root folder", it is simply a switch. It has been chosen as "switch" char because it is forbidden in file and folder names (it is a path separator), hence it cannot exist in an element name.
When you apply a folder name mask filter, only files whose path contains a matching folder are included. Moreover, folders whose names match the mask are hilighted with the BOLD style in their name. This makes easy to understand why stuff has been included by the filter. If, on the other hand, you are using an exclusion filter (by prepending the whole pattern string by the negation pipe (|) char), excluded folders are not hilighted, just because they will not be displayed.
Example: by typing \temp every file under a temp folder (at any nesting level) is included. For example, C:\Windows\temp\data\abc.txt would be included.
Example: on the contrary, by typing |\temp every file under a temp folder (at any nesting level) is excluded.
Hint: You can consider folder and file masks as a two dimensional filter. The first axis is the folder mask, the second axis is the file mask. Both axis work independently. When you apply a folder+file mask you are defining some kind of "coordinate" in a 2D space. You first "cut" the directory tree structure and isolate the searched folders, then examine the wanted file names by the other mask."
Online quick tip window:
By folder name
Same as by file name, but prepend with '\' (backslash) (|).
The folder mask considers files whose path contains elements
that match the mask at any nesting level.
Matching folders are renderer with BOLD font.
The mask itself cannot include the '\' char.
Example: \temp will include only files whose path contain
at least a 'temp' folder.
For example, C:\windows\temp\data\abc.txt is ok
Example: |\progr* will exclude files whose path contain
at least a 'progr*' folder.
The starting backslash char does not mean 'the root', it has
been choosen as switch because it is a forbidden char
in files and folders name.
(Note: Folder masks are slower than file masks)
Thanks, Umberto! :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version