10221 Include files *;*.htm fails

[chrisjj]

Name Filters, Include files: misinterprets *;*.htm as two expressions.

Until this is fixed, is there a workaround? Not "*;*.htm", I find.

Thanks.

[Michael Bulgrien]

; is used as a filter delimiter. So it would seem to me that it is being parsed correctly.

[chrisjj]

> ; is used as a filter delimiter.

In this control, newline is the filter delimiter.

> So it would seem to me that it is being parsed correctly.

If that were so, then it would appear there is no way of including ';' in the expresssion. I cannot believe that is WAD.

[Aaron]

Hello Chris,

I've added your issue as a tracker entry. Thanks for the input. For now, you will need another file filter to properly filter files that does not use a semicolon.

[chrisjj]

> I've added your issue as a tracker entry.

Thanks.

> For now, you will need another file filter to properly filter files that does not use a semicolon.

Sorry, I don't understand that. Is there a way I can include just files having ';'?

[Michael Bulgrien]

I don't have any files to test it...but have you tried this:

*[;]*.htm

[Zoë]

*[;]*.htm won't work because splitting the delimited filters up is done before anything else. That will be how the eventual fix is implemented though.

[Michael Bulgrien]

FYI - this is consistent with how filters work with other special characters. For example:

*[[]*.* for file names containing the "[" character

*]*.* is fine the way it is because there is no open square bracket to re-define the "]" character as a closing square bracket.

[Michael Bulgrien]

And another nit hardly worth fixing...but if you are going to review the logic anyway...

*[]]*.*

I would expect the [] to have no effect since there is nothing defined (empty brackets). Therefore, I would expect the above filter to be equivalent to:

*]*.*

However, in my testing, *[]]*.* doesn't filter anything...and all files are visible, not just the ones containing a "]" character.