Environment variable not resolved for menu bar [RC5 64 bit]

[Fla$her]

2AntonyD
Quotation marks, like many other special characters, can be part of a command.

[adoeller]

@ *Fla$her: I see you like finger pointing
Bygones:

Warning: Programs run as administrator will always start with the program directory as the start path, and environment variables (like %COMMANDER_PATH%) are NOT inherited from Total Commander, only those from the system. It also does not work directly with .bat and .cmd files. Please put cmd.exe /c in front of it.

Warnung: Als Administrator gestartete Programme erhalten immer das Programmverzeichnis als Startpfad, und erben keine Umgebungsvariablen (wie %COMMANDER_PATH%) von Total Commander, sondern nur die von Windows. Außerdem müssen Sie .bat und .cmd-Dateien mit vorangestelltem cmd.exe /c als Administrator starten.

The german translation is not correct and missleading, as the expansion of environment variables is linked to administrator mode and not a second independed case.

[Fla$her]

2adoeller
Finger pointing? I didn't understand.
As for not inheriting variables, this is one of the reasons why I always run TC with rights elevation.

[petermad]

2adoeller
Just use:
Command: %COMSPEC% /C
Parameters: START "" "drive:\path\exsimple.exe" %P%N "%%USERPROFILE%%\Desktop\%O.pdf" px.cfg

Then the command processer will resolve %%USERPROFILE%%

You cannot use %%$DESKTOP%% since the command processor doesn't recognize the $-environment variables.

I recommend to check the "Run minimized" ("Als synmbol") option in the button configuration.

[Fla$her]

2petermad
The author of the topic has a different nickname.
%%USERPROFILE%%\Desktop is not an optimal solution because Desktop folder can be moved from %USERPROFILE%.
You can do this:

Code: Select all

TOTALCMD#BAR#DATA
*%comspec% /q/v/c set "Desktop=%$Desktop%" &start
"" exsimple.exe %P%N "!Desktop!%O.pdf" px.cfg
plugins\wlx\ulister\demo64\document_blabla.ico
export PDF to Desktop
%COMMANDER_PATH%\plugins\wlx\ulister\demo64\
1

[petermad]

2Fla$her

The author of the topic has a different nickname.

Changed it to adoeller now.

Smart solution for passing %$Desktop% to the command processor.

[AntonyD]

2AntonyD
Quotation marks, like many other special characters, can be part of a command.

They can, but they will never be converted to the correct values of environment variables, since the probability that the description of the parameter with unusual brackets on the sides will use exactly the same character value, which is in fact the environment variable, will be very low. Such cases can be considered personally.
{%DESKTOP%}

[white]

I posted this suggestion earlier to allow environment variables in the parameter field:

2ghisler(Author)
How about solving it by accepting this syntax: %{COMMANDER_PATH}%

[ghisler(Author)]

OK, but why the trailing %? All parameters use a single percent sign.

[white]

I guess that would work too. I thought because environment variables in the Command field have this syntax: %var%. I thought it would then be easy to understand if the syntax in Parameter field was: %{var}%

[AntonyD]

I thought it would then be easy to understand if the syntax in Parameter field was: %{var}%

yep, your variant a little bit much better than mine
In this case, we definitely exclude the possibility of misunderstanding that the symbol % is not followed by a letter - which could be interpreted as the beginning of the env.variable.

[Fla$her]

the description of the parameter with unusual brackets on the sides will use exactly the same character value, which is in fact the environment variable, will be very low.
{%DESKTOP%}

But these are not quotation marks anymore. And it's better to get rid of the probabilities to the maximum. Curly brackets can be part of a name.
It's better like this: %|ENVAR|% or %*ENVAR*%
Or even better so that there is no letter from the right percent: %|ENVAR%| or %*ENVAR%*

[ghisler(Author)]

Total Commander 11 now supports a special syntax for resolving environment variables in the parameters field:
%|ENVAR|
Please note that there is only one % sign, just like all the other parameters in that field!

[Fla$her]

2ghisler(Author)
I have checked several cases. It works! Thanks, especially for the pseudo-variables!
There is no problem here either:

Code: Select all

TOTALCMD#BAR#DATA
%ComSpec% /q/k echo
%%cd%%|findstr :|find "\"
wcmicons.dll,82