Total Commander

petermad wrote: ↑2020-04-18, 20:24 UTC And what prevents you from doing that in currrent TC?

You do know that if you want to put environment variables in the "Parameters:" field of a button you have to double the %-signs - like:

Code: Select all

--disk-cache-dir=%%TEMP%%\ChromiumCache%%RANDOM%%

If you use the parameter in the "Command:" field you just use ordinary single %-signs.

I'd try both like "D:\ChromiumCache%%RANDOM%%" & "D:\ChromiumCache%RANDOM%", but I got the folder "D:\ChromiumCache%RANDOM%" twice

petermad wrote: ↑2020-04-20, 12:48 UTC 2thomasmo

I'd try both like "D:\ChromiumCache%%RANDOM%%" & "D:\ChromiumCache%RANDOM%", but I got the folder "D:\ChromiumCache%RANDOM%" twice

But did you use "D:\ChromiumCache%RANDOM%" in the Command field?

There are three options:
Either
Command: drive:path\yourprogram --disk-cache-dir=%TEMP%\ChromiumCache%RANDOM%

OR:
Command: %COMSPEC% /C start "" "drive:path\yourprogram"
Parameter: --disk-cache-dir=%%TEMP%%\ChromiumCache%%RANDOM%%

OR:
Command: %COMSPEC% /C
Parameter: start "" "drive:path\yourprogram" --disk-cache-dir=%%TEMP%%\ChromiumCache%%RANDOM%%

ghisler(Author) wrote: ↑2020-04-19, 08:14 UTC If you put environment variables in double % signs in the parameters field, they will NOT be resolved by Total Commander. They will be passed with single % signs to the target application. It's then the duty of the target application to resolve them.

If you want to resolve environment variables in Total Commander, you need to put them in the "command" field. This field also accepts command line paramters as long as you properly quote names containing spaces.

for n, param in A_Args
{
    MsgBox Parameter number %n% is %param%.
}
ExitApp

ghisler(Author) wrote: ↑2020-04-19, 08:14 UTC If you put environment variables in double % signs in the parameters field,
they will NOT be resolved by Total Commander.
They will be passed with single % signs to the target application.
It's then the duty of the target application to resolve them.

I just would not want to a commander windows flash beforce launch app

Stefan2 wrote: ↑2020-04-21, 09:53 UTC 2thomasmolover

ghisler(Author) wrote: ↑2020-04-19, 08:14 UTC If you put environment variables in double % signs in the parameters field,
they will NOT be resolved by Total Commander.
They will be passed with single % signs to the target application.
It's then the duty of the target application to resolve them.

It's then the duty of the target application to resolve them.


Use an leading ? question sign in the Parameters box to see what TC will pass to AHK.


COMMAND: xxxxx\AHK\AutoHotkey.exe xxxx\ShowParameters.ahk
PARAMETERS: ?%%TEMP%% ### %%RANDOM%%
>>>?-DIALOG Shows: %TEMP% ### %RANDOM%
>>>OUTPUT: nothing (probably %...% are variables in AHK, and that non-existing vars in the script result in empty string)

Also passing %var% to an VBS script for example
For i = 0 to WScript.Arguments.Count -1
      MsgBox WScript.Arguments.Item(i)
will not automatically expand the vars, because VBS doesn't know what you want from it.
You can pass %var%s and then handle (expand) them inside the script by using VBS functions to do that.


With CMD it will work:
COMMAND: cmd /k
PARAMETERS: ?Echo %%TEMP%% # # # %%RANDOM%%
>>>?-DIALOG Shows: Echo %TEMP% # # # %RANDOM%
>>>OUTPUT: C:\Users\Stefan2Einer\AppData\Local\Temp # # # 20050


So your program can not handle environment variables (at least not that way).
Solution: Just call a ahk script from your button, use there the EnvVars you want (or utilize AHK functions) and call your application from there.

petermad wrote: ↑2020-04-21, 13:31 UTC 2thomasmolover

I just would not want to a commander windows flash beforce launch app

Then just use the iconic=1 parameter
Or in a button check the box "Run minimized"

It will only be the DOS box that is minimized, not your application.

Dalai wrote: ↑2020-04-21, 15:11 UTC There are environment variables that are special to/in CMD: %RANDOM%, %CD%, %DATE%, %TIME%, %ERRORLEVEL% and some others (see SET /? in a CMD window). They're resolved by CMD at execution time. This means that TC won't be able to resolve any of them. Hence, the command must be executed via CMD in some way, like petermad showed in the second and third variant.

Regards
Dalai

thomasmolover wrote: ↑2020-04-22, 10:50 UTC ...
Thank you. I just think that the TC could support a direct parameter .