void wrote: ↑Fri Jul 05, 2024 10:50 pm
I will consider a limit-children: search function.
Thank you for the suggestion.
I will also consider a distinct-count: search function.
limit-children:3 would be the same as distinct:path distinct-count:3
limit-children:1 would be the same as distinct:path
distinct:path is already implemented.
I'd like to second this request, I've seen the question pop-up before namely here:
https://mail.voidtools.com/forum/viewtopic.php?t=11322 and although it may be an exotic feature it would add some enormous (IMO) power to an already phenomenal list of search functions.
I particularly have a use case for such a function along with the following search query I use:
E.g. `randomize: count:128 ext:wav length:0..3`
This typically works fine across a folder and its contents (sub folders/files) except in the case where one search (as per attached screenshot below) is searching across 10 sub-folders containing a combined 5,472 files. The randomness of the selection is highly uneven favoring those files from folders that I select first over those later.
Of the folders selected, the result set is dominated only by those files from the Kicks, Claps, and Cymbols folders.
A `limit-children:` function would be superb.
E.g. `randomize: count:128 ext:wav length:0..3 limit-children: 10`
It'd also be (I might be pushing one's luck here) awesome to have something similar to `max-limit-children: N` which would behave in an "less than or equal to N" files from children folders in the case where an exact amount is not required i.e. fixed or variable.
For my use case I wrote a separate standalone tool using Electron and NodeJS to accomplish this, though it'd be great to see such capabilities make their way into Everything.
Appreciate the consideration either way and thanks for your continued work.