Match-case bug? (Update: actually UPPERCASE EXT filter issue, when using wildcard)

[andymbody]

Update: This issue is seen when using wildcards in extension filter (ext:) list

I think there is a bug with "match-case"... Results will not find all cases (specifically uppercase) when "match-case" is turned off.

Using Version 1.5.0.1354a (x64)... (I don't know if this happens with previous versions)...

I find that... you must turn "match-case" on and specify UPPERCASE in query in order to show UPPERCASE results. Otherwise no UPPERCASE results will appear. Lower-case and camel-case results do appear.

Shouldn't UPPERCASE results be shown when "match-case" is turned off (case-insensitive)?

For instance if the query is one of the following (without "match-case" enabled):
file:doc
file:DOC

Results will be:
My1.doc
my2.Doc
document.txt
Document.txt

But will not find:
MY3.DOC

This issue also happens when filtering by ext: (and probably other filters, but I have not tested)

If I turn on "match-case", using "file:DOC" then UPPER-CASE will be found, but then no lower-case or camel-case results will show (which I would expect).

Am I missing a setting, or is this a bug?

Andy

[void]

The uppercase filenames should be found when match-case is off.

Could you please send some debug output:

• Please clear the search box and disable Match Case.
• In Everything, from the Tools menu, under the Debug submenu, check Start Debug Logging.
• Set the search to:
  file:doc
  ---wait for results to show
• From the Tools menu, under the Debug submenu, click Stop Debug Logging.
  ---Your Everything Debug Log.txt will open in Notepad.
• Could you please reply with the content of this file.

[andymbody]

"Could you please reply with the content of this file."
Yes, but...

I narrowed the cause to the wildcard character (?) for ext: filter. See screenshot...

If I do not use the (?) wildcard character, it finds the uppercase file as expected. Otherwise it omits this (and other uppercase) file(s).

I created the test folder just for demonstration purposes (obviously I would normally not use a wildcard char for exe files). I tested the WC char in different combinations and locations within the extensions, same results when included.

Do you still want a debug report?

Andy

[void]

Thank you for the ext: issue report.

This issue will be fixed in the next alpha update.

I'll make a post here once this is ready for testing.

[andymbody]

Here is a little different situation.

It found the uppercase file that matches the wildcard, but did not list the uppercase file that did not include the wildcard char.

.

[void]

The non-wildcard extension is case sensitive. (it should be case insensitive)

The issue only occurs when one of the extensions uses a wildcard.

ext:

[andymbody]

.
"The non-wildcard extension is case sensitive."
Clarification... the following also excludes the uppercase ini file.
file: setup ext:INI;inf;ex?

This bug also causes the opposite behavior when using the not (!) operator. When attempting to exclude an extension, it will instead show that extension in the search results when the wildcard is included in the extension list.

For example:
file: setup !ext:ini;inf;ex?

This will exclude all files except SETUP.INI, which will be included in search results


Thanks for the info. I will keep this issue in mind until there is a chance to address it in an update. BTW... I forgot to mention that this also happens with the (*) wildcard, but you probably already realize this.

Thanks for all that you do!!
Andy

[therube]

(I didn't realize you could even use wildcards in ext:. Thanks.
[Thinking about it though, it's more like, ext:jp*g, so why not.])

[void]

Everything 1.5.0.1355a fixes and issue with ext: matching case.

[andymbody]

Thank you!