"Search in" field now supports environment variabl

Bug reports will be moved here when the described bug has been fixed

Moderators: white, Hacker, petermad, Stefan2

Post Reply
good_alias
Junior Member
Junior Member
Posts: 20
Joined: 2006-03-01, 21:33 UTC
Contact:

"Search in" field now supports environment variabl

Post by *good_alias »

Using Total Commander 7.0 Release Candidate 1 on Vista, and read about added items in history.txt and found the interesting item Search: "Search in" field now supports environment variables like %path%. So I tried it, and TC recognize %path% but it can not find calc.exe, but if I copy the content of the path variable to the search in field, it finds three different calc.exe.

When writing this post I tried %path% again and now I get the error "Search Path not found". Instable?
User avatar
roentgen
Power Member
Power Member
Posts: 757
Joined: 2005-12-03, 19:58 UTC

Post by *roentgen »

Could be because TC only reads %path% for the current user, not the system wide %path%
Try another var, like %windir%.

With such workarounds still a bug IMO.
TC for Linux please!
good_alias
Junior Member
Junior Member
Posts: 20
Joined: 2006-03-01, 21:33 UTC
Contact:

Post by *good_alias »

I'm not sure it's that simple. I have no user secific path, only the system one. And as I wrote, after testing a while tc didn't recongnize %path% but now it kind of works again.

When TC recognizes %path% it seems it can find things in the begining of the path.

And if i search for *.* in %path% with "current dir only", I get all the files in E:\Windows (?) that is %windir% or the second entry of my path.
Could it by that it chooses the wrong variable?

Could the fact that I have no path variable for user create a problem?

My path for system, (anything special?):
PATH=E:\Windows\system32;E:\Windows;E:\Windows\System32\Wbem;E:\Program Files\Microsoft SQL Server\90\Tools\binn\;E:\Windows\system32\WindowsPowerShell\v1.0; e:\bin;f:\src\nsp\C3PO\build.mk\script\windows; f:\src\nsp\C3PO\build.mk\tools\windows\cpp; f:\src\nsp\C3PO\build.mk\tools\windows\msys\1.0\bin; f:\src\nsp\C3PO\build.mk\tools\windows\msys\1.0\mingw\bin; f:\src\nsp\C3PO\build.mk\tools\windows\msys\1.0\mingw\libexec\gcc\mingw32\3.4.2; F:\Program Files\svn-win32-1.4.3\bin
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48205
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Indeed RC1 only reads the first 259 characters of environment variables. This will be changed to 2kBytes in the next RC.
Author of Total Commander
https://www.ghisler.com
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48205
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Should work now with up to 2kBytes environment variables, please check!
Author of Total Commander
https://www.ghisler.com
good_alias
Junior Member
Junior Member
Posts: 20
Joined: 2006-03-01, 21:33 UTC
Contact:

Post by *good_alias »

I will
good_alias
Junior Member
Junior Member
Posts: 20
Joined: 2006-03-01, 21:33 UTC
Contact:

Post by *good_alias »

Seems to work very nice, tested on Vista with the path variable, mentioned above.
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48205
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Thanks for checking!
Author of Total Commander
https://www.ghisler.com
Post Reply