[TC 11.03] Search for \ and leading and trailing spaces

[white]

Search text to search for all files, do not search in subfolders:

Code: Select all

\

Add 1 trailing space and it still works. But if you add more trailing spaces, it no longer works. And if you add any leading spaces, it also doesn't work.

[ghisler(Author)]

Sorry, I do not understand your report. What are you trying to achieve?

[petermad]

2ghisler(Author)

I think White expects expects all leading or trailing spaces to be ignored.

[white]

Sorry, I do not understand your report. What are you trying to achieve?

Like I said: "search for all files, do not search in subfolders". The search text contains an empty mask for searching files/folders, which in Total Commander means *.*, and an empty include only traverse folder "\". So traverse only the folder with an empty name . After adding 1 trailing space, it still works. But with more spaces added or with leading spaces added, it no longer works.

I think White expects expects all leading or trailing spaces to be ignored.

Correctamundo. The results should be the same as when using no spaces or 1 trailing space.

[jonathanpoulin]

Interestingly, this search string below works (2 leading\trailing spaces, 2 between tokens).

Code: Select all

  \  *.*  

So, it doesn't work only when "empty mask" is used.

2white

Was it working in previous TC version?

[white]

So, it doesn't work only when "empty mask" is used.

Correct, that is what I am addressing. The issue isn't limited to only using a single "\" with one or more spaces. The same applies to searching for, for example, "dir\" when you have a folder called "dir".
So this example with an empty mask for file/folder specification also works:

Code: Select all

dir\

This is essentially the same as "dir\ *.*" or "*.* dir\"
After adding one trailing space to the code, it still works. But adding more spaces, or adding leading spaces, causes it to no longer work.

Was it working in previous TC version?

This is working this way since version TC 11.00b7 (nothing relevant in HISTORY.TXT AFAIK).
Before that, an empty mask for file/folder specification in combination with an include only folder wasn't supported. It did however work with exclude, for example:

Code: Select all

| dir\

This did and does the same thing as "*.* | dir\"
However, when you add leading spaces to the code, it no longer works. As reported in my other bug report.

[ghisler(Author)]

Please use
*.* \
to find all files and subfolders in the current directory, but nothing in subdirs.
\
alone isn't defined, it also finds nothing with Everything, while *.* \ does.

I'm sorry but I will not try to detect all possible invalid or undocumented search strings and show errors when I encounter them. I would be doing only that for the next 10 years.

[white]

Please use
*.* \
to find all files and subfolders in the current directory, but nothing in subdirs.
\
alone isn't defined, it also finds nothing with Everything, while *.* \ does.

I'm sorry but I will not try to detect all possible invalid or undocumented search strings and show errors when I encounter them. I would be doing only that for the next 10 years.

1) You act like it's weird to enter nothing if you want to search for all files/folders. But it has been this way since at least Windows Commander 3.03 (I checked). And I don't think it's an accident that searching for "dir\" or "|*.bak" assumes * as the file/folder mask.

2) *.* stems from the MS-DOS era and is also not documented. Nowadays it makes more sense to talk about using *.

3) You've added more and more complexity by adding functionality to the same 'Search for' field over and over again. The help text is very poor at explaining, so the functionality is actually badly documented.

[tuska]

\
alone isn't defined, it also finds nothing with Everything, ...

No, it only finds folders in 'Everything' and TC (ev:\).
You get the same result with the 'Everything' modifier: ... folder:

Everything 1.5.0.1383a (x64)

[JOUBE]

The results should be the same as when using no spaces or 1 trailing space.

No.

2) *.* stems from the MS-DOS era and is also not documented. Nowadays it makes more sense to talk about using *.

No.

[petermad]

The results should be the same as when using no spaces or 1 trailing space.

I agree. Spaces should only be recognized as such if they are quoted.

[JOUBE]

Spaces should only be recognized as such if the are quoted.

No.

[ghisler(Author)]

This should be fixed in Total Commander 11.50 beta 1, please check it!

17.07.24 Fixed: Find files: Ignore any leading and trailing spaces in wildcard searches except when they are in double quotes, e.g. *.txt *.docx now needs to be "*.txt " *.docx (32/64)

[white]

Tested OK using TC 11.50b1 32-bit.
One issue remains when using TC 11.50b1 64-bit: the issue when with leading spaces.

[ghisler(Author)]

Confirmed, although I copied the code to 64-bit it behaves differently.