List of environmental variables

[eydaimon]

Couldn't find a list of environmental variables in the helpfile. Would be nice if there was a topic containing all of them. Also didn't find any topic containing them. The only thing I've seen to use as a reference for this is the "What's new in this version?" or changelog.

List please? add to help file please?

[icfu]

http://www.ghisler.ch/wiki/index.php/Navigation

TC 7 adds more, you should inspect the history.txt which is the source also for the Wiki article.

Icfu

[nsp]

http://www.ghisler.ch/wiki/index.php/Navigation
.... snip ...

%COMMANDER_DRIVE%, %COMMANDER_INI% are missing in the wiki document.

And only

Code: Select all

COMMANDER_PATH
COMMANDER_DRIVE
COMMANDER_INI

are passed by TC in the current environment and can be used internally by external program and/or bat file launched by a Button, Hot key, .....
All the virtual var are translated in all command/parameter section by TC before the call.

[icfu]

This is what I mean with "TC 7 adds more" above...

%COMMANDER_INI% isn't missing, it's there.

Icfu

[nsp]

This is what I mean with "TC 7 adds more" above...

%COMMANDER_INI% isn't missing, it's there.

Icfu

Sorry i've just given a quick look and did not saw Commander_(the ordering by name is missing in the wiki

[icfu]

Oh, and we have a new Wiki editor now! Welcome!

I have also added the other new vars in the Wiki, for future reference also here again:

Code: Select all

%COMMANDER_DRIVE% (TC 7)
%COMMANDER_INI% (TC 7)
%COMMANDER_PATH%

%U3_DEVICE_EXEC_PATH%

%$APPDATA%
%$COMMON_APPDATA%
%$COMMON_DESKTOPDIRECTORY%
%$COMMON_DOCUMENTS%
%$COMMON_PICTURES%
%$COMMON_PROGRAMS%
%$COMMON_STARTMENU%
%$COMMON_STARTUP%
%$DESKTOP%
%$FONTS%
%$LOCAL_APPDATA%
%$MYMUSIC% (TC 7, XP only)
%$MYPICTURES%
%$MYVIDEO% (TC 7, XP only)
%$PERSONAL%
%$PROGRAMS%
%$STARTMENU%
%$STARTUP%

Icfu

keywords: pseudo environment variable variables env var vars envvar envvars

[menet]

I have also added the other new vars in the Wiki, for future reference also here again:

Code: Select all

%COMMANDER_DRIVE% (TC 7)
%COMMANDER_INI% (TC 7)
%COMMANDER_PATH%

%U3_DEVICE_EXEC_PATH%

%$APPDATA%
%$COMMON_APPDATA%
%$COMMON_DESKTOPDIRECTORY%
%$COMMON_DOCUMENTS%
%$COMMON_PICTURES%
%$COMMON_PROGRAMS%
%$COMMON_STARTMENU%
%$COMMON_STARTUP%
%$DESKTOP%
%$FONTS%
%$LOCAL_APPDATA%
%$MYMUSIC% (TC 7, XP only)
%$MYPICTURES%
%$MYVIDEO% (TC 7, XP only)
%$PERSONAL%
%$PROGRAMS%
%$STARTMENU%
%$STARTUP%

Icfu

Will all these variables be documented inside the HELP file of Total Commander 7 ?

Best regards

[AlleyKat]

Ahh, excellent thread guys, just the info I needed. For some reason I couldn't find that page by searching in the wiki - no idea why, it does turn up now, even thou it's not the most obvious of names. A separate page listing the environ vars would be nice too.

I use this for my portable 'office' pack, PortableApps suite + various PortableApps apps + TotalCommander on a USB stick. Let me repeat what I've stated before, the tc2usb transfer tool rocks!!! - thou I'd still love it even more if it would include some predefined subfolder (either to the TC exe or to the GHISLER profile data folder) for various small exe based tools that are usually used with TC (examples: XVI32, newfile.exe).

This enables me to change my normal PuTTY toolbar button to a PuTTY Portable button just by changing the paths to "%COMMANDER_DRIVE%\PortableApps\PuTTYPortable\" - totally awesome.

Kinda a shame that the tc2usb tool doesn't fix fixed-path icons in toolbars, at least when they're pointing to the TC program folder anyway - but then again, that'll teach me to use relative paths I guess...


Off-topic, the wiki throws some strange errors in some cases, even for existing pages (example, 3rd link on this page) - seems to be an issue with links (also true for searches) including the % percentage symbol.

[MVV]

Be careful, not all variables listed in icfu's post are real environment variables, most of them are pseudo-variables that are used only by TC itself and are invisible for child processes.
You may start command line from TC and execute set command to see which variables are real ones and are available for all child processes (e.g. variables listed by nsp).

[Balderstrom]

Or you can just make your own ENVironment VARS (in a .cmd that launches TC), then you know for sure they exist
And don't have to use the uncommon %$FOO% syntax.

You can also add Permanent and "Volatile" environment vars. That are stored in the registry.

My favorite is:

SET AHK="%ProgramFiles%\AutoHotKey\AutoHotkey.exe" "%ProgramFiles%\AutoHotKey\Sc
ripts"

Which let's me launch AHK scripts from TC buttons/user-commands, by just filling in: %AHK%\ScriptName.ahk