Bug in the 'Find Files'?

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

Moderators: white, Hacker, petermad, Stefan2

Post Reply
User avatar
bdk
Junior Member
Junior Member
Posts: 34
Joined: 2006-11-24, 09:32 UTC

Bug in the 'Find Files'?

Post by *bdk »

Hi

I think I have found a bug in 'Find Files'. I think the | option is broken.
To reproduce:
Create a directory called test, create two subdirectories in test called main and target. Create a file called fileToFind in each of these subdirectories.
Now navigate back to directory test and invoke Find Files.
Try searching for 'fileToFind'. You will find both files.
Then try to search using 'fileToFind | target\' and you will find none!!
The file under main should be found, but is not.

Can anybody else reproduce? Or am I doing something wrong?
I am pretty sure this functionality worked prior to TC 7.5.

regards,
bdk
yeskky
Member
Member
Posts: 177
Joined: 2007-03-01, 05:32 UTC
Location: Jiang Su,China

Post by *yeskky »

I don't think it's a bug.Read help file first please.

New: Include/Exclude certain directories in the search. Wildcards can be used in include/exclude directory names, and the names must have a trailing backslash \ .
Examples:
*.ini | windows\ finds all ini files except those in directories called "Windows" and their subdirs.
#222405 Single user licence
User avatar
petermad
Power Member
Power Member
Posts: 14814
Joined: 2003-02-05, 20:24 UTC
Location: Denmark
Contact:

Post by *petermad »

You have to put a wildcard in the filename for this to work.

If you search for *fileToFind | target\ it will work.

But I admit that it is not very consistant that searching for fileToFind works while searching for fileToFind | target\ doesn't.
License #524 (1994)
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
User avatar
bdk
Junior Member
Junior Member
Posts: 34
Joined: 2006-11-24, 09:32 UTC

Post by *bdk »

Thanks for your replies.
I have read the help file, and I never interpreted that you HAVE TO use wildcards in the filename to make the | work, just that you CAN use wildcards.
But now I know. :-)

If there is not a very technical reason for the inconsistent behavior 'petermad' points out I really think it should be fixed.
User avatar
white
Power Member
Power Member
Posts: 4626
Joined: 2003-11-19, 08:16 UTC
Location: Netherlands

Post by *white »

Confirmed.

It looks like when there are no wildcard characters or dots in the the Search for field, the pipe symbol (|) is not interpreted and file names are compared with the contents of the whole Search for field.

Just adding a dot does work:
fileToFind | target.\

or:
fileToFind. | target\

I agree that it should be fixed or at least explained better in the help.


BTW. It does not matter where the wildcard character is used. The following examples also work:
fileToFind | target*\
fileToFind | *target\
fileToFind | tar*get\
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48096
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Sorry, the pipe symbol is only interpreted while in wildcard search mode. I will try to support it also in other modes.
Author of Total Commander
https://www.ghisler.com
Post Reply