[BUG] Search: Names with semicolons are not found

[icfu]

1. Create a file: c:\te;st.txt
2. Search for "te;st.txt"
=> Nothing found.

3. Search for "te;st"
=> It's found.

Icfu

[StickyNomad]

Confirmed.

[sas2000]

 

1. Create a file: c:\te;st.txt
2. Search for "te;st.txt"
=> Nothing found.

3. Search for "te;st"
=> It's found.

Confirmed ++, but you can find it this way :

1. Search for "te;st.txt"
=> Nothing found.

2. Search for "te;st.txt" RegEx activated
=> It's found.

[StatusQuo]

1. Create a file: c:\te;st.txt
2. Search for "te;st.txt"
=> Nothing found.

3. Search for "te;st"
=> It's found.

Confirmed.

2. Search for "te;st.txt" RegEx activated
=> It's found.

Almost confirmed:

Search for "te;st.txt" RegEx activated
=> Nothing found.

Search for te;st.txt RegEx activated (no quotes surrounding the name)
=> It's found.

[sas2000]

 

2. Search for "te;st.txt" RegEx activated
=> It's found.

Almost confirmed:

Search for "te;st.txt" RegEx activated
=> Nothing found.

Search for te;st.txt RegEx activated (no quotes surrounding the name)
=> It's found.

When i wrote "te;st.txt" i meant te;st.txt without quotes ( obviously ).
 

[ghisler(Author)]

This is also intentional, the ";" character was initially used to separate name parts, which was later changed to a space - but the ";" is still allowed for backwards compatibility when the search string contains a dot.

[StatusQuo]

However, if semi-colons are problematic,
shouldn't surrounding quotes lead TC to treat the name as typed?

Including the quotes and having RegEx not checked,

• "te st.txt"

is found,

• "te;st.txt"

is not.
Quite odd, isn't it?

"No files found" doesn't mean what I would expect in this case.
If this can't be fixed, this limitation should at least be in the help then, IMO.

[sas2000]

 

However, if semi-colons are problematic,
shouldn't surrounding quotes lead TC to treat the name as typed?

It seems the best solution, support.