Search does not work when there is a fullstop in file name

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: Hacker, petermad, Stefan2, white

Post Reply
davidsx
New Member
New Member
Posts: 1
Joined: 2007-11-25, 17:46 UTC

Search does not work when there is a fullstop in file name

Post by *davidsx »

Search does not work when there is a fullstop in file name for example if one searched for abc25.11 hoping to try and find this file. abc25.11.2007.exe no results would be returned
User avatar
Clo
Moderator
Moderator
Posts: 5731
Joined: 2003-12-02, 19:01 UTC
Location: Bordeaux, France
Contact:

Wildcards ?

Post by *Clo »

2davidsx

:) Hello ! Welcome aboard !
…if one searched for abc25.11 hoping to try and find this file. abc25.11.2007.exe…
• Is the file-name file. abc25.11.2007.exe really ?
So, you could enter :

Code: Select all

*.*abc25.11.*
BTW : I don't see the need to have a space there, or is it accidental ? :roll:

:mrgreen: Kind regards,
Claude
Clo
#31505 Traducteur Français de TC French translator Aide en Français Tutoriels Français English Tutorials
StatusQuo
Power Member
Power Member
Posts: 1524
Joined: 2007-01-17, 21:36 UTC
Location: Germany

Post by *StatusQuo »

2davidsx
file. abc25.11.2007.exe
I guess this should read like: file: "abc25.11.2007.exe"

The behaviour probably is because if no dot is contained in the search string,
with search string text TC searches for *text* (finding also "testtext2.txt"),
but searches for the exact file name, if the search string contains a dot, like text.txt (not finding "text2.txt" nor "text.txt2").

Explained here: http://ghisler.ch/board/viewtopic.php?p=37806#37806

Solution: search text abc25.11* should find your file.
Who the hell is General Failure, and why is he reading my disk?
-- TC starter menu: Fast yet descriptive command access!
Post Reply