"!a OR b" includes "Membership_transter_form.pdf"-Why

[armsys]

"!a OR b" includes "Membership_transter_form.pdf", even though it contains "a". Why?

[admin]

Because it contains a "b"?

[armsys]

Because it contains a "b"?

While both "3239043b389bb65bd0a1ed3fbd539f7e.jpg" and "Membership_transter_form.pd" contains "a" AND "b", "!a OR b" excludes the former but includes the latter. Why?

[LittleBiG]

Because the "!a or b" is evaluated as standard, not boolean in your case.

EDIT:
However, I feel a little bug here. If master invert is unset and no smart detect of boolean, the "!a or b" should mean

Code: Select all

"!a" and "or" and "b"

Now ! is simply omitted.

[armsys]

Because the "!a or b" is evaluated as standard, not boolean in your case.
EDIT:
However, I feel a little bug here. If master invert is unset and no smart detect of boolean, the "!a or b" should mean

Code: Select all

"!a" and "or" and "b"

Now ! is simply omitted.

Bingo! You're absolutely correct. By examining hundreds of file names one by one, it took me innumerous hours to reach the same conclusion. I discover each found item contains "or". Then, I realize I was fooled and misled by the beta log. In a glimpse, in the whole context of the beta log, you won't possibly doubt the "OR" as a logical operator. In fact, it's untrue. the "OR" is interpreted as a literal string "or". Don never hints the possibility of the Standard mode and the pattern being interpreted as a character string. On the contrary, Don worsens our confusion by the annotation of "NOT (a OR b)".

[armsys]

My repeated tests confirm v15.70.0129 removes all recently mentioned minor 'File Files' anomalies.
While the "Enable extended pattern matching" option being disabled, in File Files, the !a or b pattern can include, say, "!aUR_Lib_Import.txt", as expected.
Nonetheless, referring to the v15.70.0129 beta log,

Code: Select all

Without Extended Pattern Matching and no Boolean mode this should be interpreted like this:
"!a" AND "or" AND "b"

For clarity, I would rephrase it as:
Without Extended Pattern Matching and no Boolean mode, while still observing LBM, this should be interpreted like this:

[armsys]

Referring to the v15.70.0129 beta log, Don took painstaking efforts in augmenting clarity in the following ofttimes overlooked nuances:
1. Find Files vs. Quick Search. (The most important one!)
2. Factory vs Non-Factory defaults in respect of FindAllowMasterInvert.
3. "Enabled extended pattern matching" option.
Thank you Don.

[admin]

My repeated tests confirm v15.70.0129 removes all recently mentioned minor 'File Files' anomalies.
While the "Enable extended pattern matching" option being disabled, in File Files, the !a or b pattern can include, say, "!aUR_Lib_Import.txt", as expected.
Nonetheless, referring to the v15.70.0129 beta log,

Code: Select all

Without Extended Pattern Matching and no Boolean mode this should be interpreted like this:
"!a" AND "or" AND "b"

For clarity, I would rephrase it as:
Without Extended Pattern Matching and no Boolean mode, while still observing LBM, this should be interpreted like this:

OK, right.