ext: wildcards

[uncleBob]

back in April of 2022 you fixed alpha version 1.5 so that ext:xlsx;xlsm works properly.

That was very helpful, but supporting wild cards in Extension: would be even more helpful. ( In fact wild cards should also be considered for most of the properties that can put into a delimited list. )

Let's say I want to find an old financial planning file but I don't remember its exact name or if it was excel, word, or power point

with version 1.5 I can search for name:finan;plan ext:xls;xlsx;xlsm;xlst;doc;docx;docm;ppt;pptx

But its very ugly. And of course the above list of extensions omitted xlsb or xla and maybe even a few others.

Wild cards would make a huge difference:

name:finan;plan ext:xl*;doc*;pp*

Please consider it.
uncleBob

P.S. By the way Everything.exe is great and in many ways superior to x1.com which I have been using for 20 years.

[void]

Thank you for your feedback uncleBob,

The next alpha update will support * and ? wildcards with ext:

Thank you for the suggestion.



extension: should already support wildcards.
As do other functions that accept "filename" parameters. (eg: stem: name: child: parentname: ancestorname: etc..)
I'll also fix wildcard highlighting in the next alpha update.

[uncleBob]

WOW, your response was almost as fast as Everything.exe ! Thanks

Bob

[Michi]

Considering that extensions could be longer than one, two or three characters, like.config for example, supporting wildcards would be awesome!
This way I could find files or folder, too, like ext:conf*

[void]

Everything 1.5.0.1336a adds wildcard support to ext:

For example:
ext:mp*
ext:conf*

Everything 1.5.0.1336a also fixes an issue with wildcard highlighting.

[Michi]

Great! Thanks for this!

[void]

Everything 1.5.0.1338a fixes the following issues with ext:

Using wildcards with ext: will now highlight correctly.

For example:
ext:mp*



The *. prefix is now removed.

For example:
ext:*.mp3

[rnbrito]

Can you consider add the # (single digit) wildcard support to ext: as well?

That would solve the search without using regex for programs thatgenerate extensions with only numbers (f.e. when splitting an archive with 7-zip: 7z.001, 7z.002, etc. The search query for those files would be ext:7z.###)
and others that modify their default extension by replacing a part with numbers (f.e. when creating a disk image split by a fixed size within DriveSnapshot: sna, sn1, sn2, s20, s45. The search query for those files would be ext:sna;sn#;s##)

Thanks!

Thank you for your feedback uncleBob,

The next alpha update will support * and ? wildcards with ext:

Thank you for the suggestion.



extension: should already support wildcards.
As do other functions that accept "filename" parameters. (eg: stem: name: child: parentname: ancestorname: etc..)
I'll also fix wildcard highlighting in the next alpha update.

[void]

I will consider support for digit matching with #.
Thank you for the suggestion.

For now, the following will work:

wildcards:*.7z.###

wildcards: enables extended wildcards which has support for digit matching with #

[uncleBob]

[therube]

Webpage says, Default: Use Tools -> Options -> Advanced -> wildcards. (disabled by default)

But it looks like default is true?
And yet, set to true,

[456].7

does not find, MI.2605.7z, where

wildcards:[456].7

does?

[void]

Webpage says, Default: Use Tools -> Options -> Advanced -> wildcards. (disabled by default)

Thanks for pointing this out therube,

Tools -> Options -> Advanced -> wildcards enables/disables the basic filename wildcards.
(not the extended wildcards)

I have updated filename-wildcards:
Default: Enabled.
to:
Default: Use Tools -> Options -> Advanced -> wildcards. (enabled by default)

I have updated wildcards:
Default: Use Tools -> Options -> Advanced -> wildcards. (disabled by default)
to:
Default: Disabled.

There's no option to enable extended wildcards by default.

[therube]

no-filename-wildcards:

Literally reads "no-"...
Is that meant to be, or did you just want,

filename-wildcards:

?

[void]

I will leave it as only no-filename-wildcards: since this is the only useful use case.

You'll never manually enable filename-wildcards: as its typically enabled by default.

It was initially added as a way to match

*

and

?

in filenames.

Example usage:

no-filename-wildcards:?

While you can't have ? in filenames, it does match all Unicode ? variants, so it can be useful.



edit:
I will drop no-filename-wildcards: from the documentation.
It's not really a practical search modifier.
no-wildcards: has the same effect.

I have updated no-wildcards: