i suppose if
a or b, then allows you to use "or" in search
where
a OR b, does an a | b
(anyhow, as they're case sensitive, maybe ?... ought to say so )
(if it doesn't say,
you say, oh, it works, yeah!
then, you say, what? why isn't it working [the next time]?!)
void wrote: Tue Jan 10, 2023 4:57 am
Literal operators are case sensitive.
Hi Void; you can tell where I am up to by the content of my questions!
When checked OFF, the setting ”Allow literal operators” could be reworded as “Allow and, or and not to match parts of filenames” and as well “Allow AND, OR and NOT to match parts of filenames”.
That is, it is not so much a case of case-sensitivity as much as in/excluding the three operator [alphabetic] strings from contention.
Is the above text correct?
My feeling is for me to continue to use <space> to represent AND, ! to represent NOT, and | to represent OR.
Cheers, Chris
When checked OFF, the setting ”Allow literal operators” could be reworded as “Allow and, or and not to match parts of filenames” and as well “Allow AND, OR and NOT to match parts of filenames”.
That is, it is not so much a case of case-sensitivity as much as in/excluding the three operator [alphabetic] strings from contention.
Is the above text correct?
Yes.
If enabled, AND, OR and NOT are case sensitive.
You can also use double quotes to escape operators.
pop up in the result List..
The leading quotes tells the preprocessor(???) to treat the following characters as a literal string.
I think that is right.
Thanks, Chris