Declaring excludes in a script ?

[poutnik]

Hi,

I did not find possibility to declare excludes in a script on the only place.

I think a excluding option keyword should be implemented,
either in scope of whole script, or within VolumeSelect.

I know about options to use "-e excludes" CL script parameters,
or using Fileselect "Selection and not(excludes)" in every zone.

Did I miss anything ?

[jeroen]

You can exclude anything you want with the AND, OR, and NOT keywords in the VolumeBoolean and FileBoolean sections, but you already know that? I think I don't understand what you are proposing.

[poutnik]

As far as I understand,
Volumebooleans are limited in usable keywords and Filebooleans need to repeated for every zone.

Well, there is ImportListfromFile within Volumeboleans, not yet implemented.
Does it support wildcards ?

[jeroen]

As far as I understand, Volumebooleans are limited in usable keywords

Why do you say "limited"? I think it is extremely flexible and powerful. What is missing?

Well, there is ImportListfromFile within Volumeboleans, not yet implemented. Does it support wildcards ?

Well, no, my design is to import a list of literal paths, 1 path per textline.

[poutnik]

First to note that my original intention was not pushing you to implement anything,
but my afraid I have missed something in doc. I am sorry if I have made you feeling different.

As far as I understand, Volumebooleans are limited in usable keywords

Why do you say "limited"? I think it is extremely flexible and powerful. What is missing?

Well, as academical, hypothetical and not necesserily useful example:

Imagine I need to exclude all *.ext files, created at least 2 days ago, modified today that are not fragmented.

I do know I can use repeated filebooleans for that in zone fileselects.

But I do not know how to do it in volumebooleans by listed functions,
unless I missed I can use fileboolean functions in Volumebooleans too.

By other words, what is script counterpart to /*EXCLUDE*/,
if I do not want to use CL  ?

[poutnik]

when looking at VolumeBoolean functions, I miss there simple function with relative approach :

AverageFragmentation(float).

E.g:  AverageFragmentation(0.01) would defragment volume,
if there is 1 extra fragment for every 100 files.

[jeroen]

I am sorry if I have made you feeling different.

Thanks, but I was not offended in any way. I was just asking for more information.

I do know I can use repeated filebooleans for that in zone fileselects.

Yes, this is the only way to do it. It is not possible to use FileBoolean keywords in a VolumeBoolean. Does that answer your question?

p.s. I have learned an hour or so ago that the "-e" commandline option in MyDefrag v4 is not the same as for JkDefrag v3. I will have to do something to make it possible that (a selection of) files are treated as completely unmovable, like in v3.

[jeroen]

AverageFragmentation(float).

Thanks for sharing your idea, I appreciate it! I will put it on the wishlist.

[poutnik]

I do know I can use repeated filebooleans for that in zone fileselects.

Yes, this is the only way to do it. It is not possible to use FileBoolean keywords in a VolumeBoolean. Does that answer your question?

p.s. I have learned an hour or so ago that the "-e" commandline option in MyDefrag v4 is not the same as for JkDefrag v3. I will have to do something to make it possible that (a selection of) files are treated as completely unmovable, like in v3.

I feel answered, it is confirmation that things are set by way I have supposed.

Creation often makes surprice even to its creator 

[poutnik]

p.s. I have learned an hour or so ago that the "-e" commandline option in MyDefrag v4 is not the same as for JkDefrag v3. I will have to do something to make it possible that (a selection of) files are treated as completely unmovable, like in v3.

I have noticed it yesterday when trying to exclude $MFT