TC 9.50b1 - Field "Search in:" empty - Parameter ed:

[tuska]

TC 9.50ß1 x64/x86 behave differently,
if the field "Search in:" is empty and the parameter ed: is used.

x64
searches from the current directory in TC => expectation conform!

x86
will not find any files if the "Search in:" field is empty.

Please adjust x86.

Thank you!

[petermad]

I cannot confirm this - here 64 and 32 bit TC 9,5b1 behaves the same

[tuska]

Interestingly enough, it works for me every time today,
while yesterday it didn't work zig times in the 32bit version.

I don't think it works 100% every time and if you want to be on the safe side,
you should enter the path.

So I can't reenact when it doesn't work.

I would like to mention that I always start the search with a shortcut,
- where a separate window is opened
- ed: is entered in the field "Search for:"
- with an AHK script that positions the cursor after ed: (this works always)

This usually works very well.
But perhaps this combination carries the risk that sometimes it doesn't work as desired (32 bit).

For this reason, I would ask you to regard this topic as irrelevant at the moment.*)

*) There must be a difference between 32 bit and 64 bit version,
because just now 18.10.2019 15:08 the search with the 32 bit version did not work several times,
but the 64 bit version worked without problems.

Unfortunately I can't find out when the 32 bit version works and when it doesn't.

[ghisler(Author)]

Where did it search when it failed? Maybe in the directory of the target panel?

[tuska]

Where did it search when it failed? Maybe in the directory of the target panel?

No, in this case, the 32 bit version has

1. a completely wrong result (more rarely)
Example:
Search in separate window
Search in: Field is empty! --> the path to search in is: D:\Daten\WINWORD\ !!!
Search for: ed:text
Search result: 91 files and 5 directories from drive C: !!!
Close TC and restart
Search result: as before

2. no result
Example as before
Search for: ed:zeichen (other keyword)
Search result: [No files found]

In both cases I got a correct search result in the 64 bit version.

---

EDIT:
I was able to recreate the behaviour described a little later at about 19:40
and sent 2 videos (64bit, 32bit) via email to support.

[ghisler(Author)]

It looks like there is no base directory with the method you use, so TC doesn't pass the ed: parameter to Everything. What should I do? Just search everywhere?

[tuska]

It looks like there is no base directory with the method you use, so TC doesn't pass the ed: parameter to Everything.

In the 64bit version it seems to work fine for me --> No problems with search results so far!

EDIT:
The problem with the 32 bit version is that it doesn't work always.

Code: Select all

- 21.10.2019 ca. 7:00 p.m. Again start of testing with 32 bit version
  With approx. 10(!) tests there was no error! (In between 64 bit version used, 32 bit version closed and opened)
  
- 21.10.2019 ca. 8:00 p.m. Error in the 32bit version! (only 1 test done) --> [No files found]
- 22.10.2019 ca. 1.00 a.m. Error in the 32bit version! (only 1 test done) --> [No files found]

---

What should I do? Just search everywhere?

No, for this case we have parameter ev: ...

Please search with ed: in the active window = the path shown in the path line of TC.
(The directory depth (default: all (unlimited depth) can be set by anyone).
(= analogous to 64 bit version)

Example:
I:\Data\Winword\*.*

Thank you!

[tuska]

What should I do? Just search everywhere?

Please search with ed: in the active window = the path shown in the path line of TC.

In other words, to be on the safe side:
In the field "Search in:" that path should be used, which would also be used for ALT+F7 or ALT+SHIFT+F7.

This path at ed: should not be visible in the field "Search in:",
so that the path of the active TC window is always used when a directory is changed.

See also above last test results in the code field. This continues today as follows:

Code: Select all

22.10.2019 ca. 10:49 a.m. Error in the 32bit version! (only 2 tests done) --> [No files found]

[tuska]

Code: Select all

30.10.19 Release Total Commander 9.50 beta 3
25.10.19 Added: Find files: For test purposes, when searching with option ed:, 
put the used start path in the "Search in:" field when the field was empty (32/64)

A search with the self-defined shortcut CTRL+F brings the following:
- It is always searched only in path C:\WINDOWS\system32\ (TC 9.50ß3 32bit)
- Each time the window size is changed, the path in the "Search in:" field is immediately removed (TC 9.50ß3 32 + 64 bit)
- TC 9.50ß3 x64: Search still works

[ghisler(Author)]

Interesting - C:\WINDOWS\system32\ is the current directory when I launch a program with different user rights. It doesn't inherit the current directory from the calling program then.

Do you launch the external search with admin rights?

[tuska]

Interesting - C:\WINDOWS\system32\ is the current directory when I launch a program with different user rights.
It doesn't inherit the current directory from the calling program then.

Do you launch the external search with admin rights?

No (Hardcopy available).

But if I now start TC 9.50b3 with admin rights,
then the search query suddenly works well
- with admin rights and afterwards
- also without admin rights

I'll do more tests with the 32bit version.

[tuska]

Now I have made an interesting discovery.

TC 9.50b3 32bit as User and as Admin:

Code: Select all

1. button with command: OPENLANGUAGEFILE WCMD_eng.LNG --> 9.50b3 32bit --> search results (paths) correctly available!
2. button with command: OPENLANGUAGEFILE WCMD_deu.LNG --> 9.50b3 32bit --> C:\WINDOWS\system32\ --> Wrong!

I'm using the right file: WCMD_DEU.LNG.

This problem does not exist in the TC 9.50b3 x64 version.

[ghisler(Author)]

Sorry, no idea. Maybe not enough space in environment, whatever - the search just get the current dir from the caller.

[tuska]

Please watch this video.

EDIT:
Link modified

[petermad]

2tuska

1. button with command: OPENLANGUAGEFILE WCMD_eng.LNG

I can see from your video, that you don't actually have a WCMD_eng.LNG file - hence TC defaults to internal English.

Could you try it using an actual English .lng file - you can download one here: https://madsenworld.dk/tcmd/TC95b3Language.zip