Website and Help Typos

[admin]

"... shows that semicolons after the cases are an acceptable alternative to colons: ..."

[highend]

oh... that looks... weird...

[admin]

PHP has it too.

[highend]

that doesn't make it less weird

[admin]

A little less for those who know PHP.

[highend]

property()
XYplorer-specific Special Properties

#ItemCount = Number of items (files and folders) in a folder (non-recursive); "" (nothing) if folder unavilable

[admin]

Merci!

[highend]

Visual Filters
Must-Match-Patterns

nec:a;b;nec:c;d = a AND (b OR (c AND (d OR e)))

Am I missing something or isn't there an "e" in the left pattern?

[admin]

Indeed, the error is was already in the change log. It should be:

Code: Select all

nec:a;b;nec:c;d               = a AND (b OR (c AND d))

[highend]

The "Path" checkbox in the find files tab has a popup tooltip. The latter part states

Any backslashes must be doubled ("\\") in the search term.

I guess this was made for the regex mode? Maybe a further explanation should be
added...

[admin]

The "Path" checkbox in the find files tab has a popup tooltip. The latter part states

Any backslashes must be doubled ("\\") in the search term.

I guess this was made for the regex mode? Maybe a further explanation should be
added...

No, it's other reasons related to the parsing of complex terms. Internal stuff...

[highend]

I see but even when putting a double quoted path in it, it didn't require doubled backslashes to work correctly...

[admin]

Isn't this mentioned in Help?

Alternatively to adding backslashes, you can quote the pattern to protect it from parsing:
:!"*\temp\*"
:"*\keyboard*" OR "*\mouse*"

[highend]

No clue. No one actually reads help files nowadays...

[admin]

OK, but I don't think anything needs to be done. The tooltip is sufficient. It's not the place to answer the "Why?" question.