User Command for hashing console programs

[Axis]

Like I said, here works with absolute paths only:

Command: c:\tc\utils\lst2mlt\lst2mlt.exe

Parameters: /X:"c:\tc\utils\DirHash\DirHash.exe" /L:"%L"

It works

[hi5]

Yes of course that works, do you see the difference?

Code: Select all

      utils\lst2multi\lst2mlt.exe
c:\tc\utils\lst2mlt\lst2mlt.exe

\lst2multi\ v \lst2mlt\

Edit: my bad, my path was lst2multi

[Axis]

My path to lst2mlt.exe is utils\lst2mlt\ NOT utils\lst2multi\

[hi5]

Are you sure you don't have a space before " utils\" because if the full path works just "utils\" will to. There must be a typo, can't help you further.

[Axis]

Are you sure you don't have a space before " utils\" because if the full path works just "utils\" will to. There must be a typo, can't help you further.

Super-sure (I've retested)

Thanks (maybe a bug in 9.22?)

[hi5]

No as I've just tested it. What is in your start path? "c:\totalcmd\" in mine. If you copy this and paste it in your buttonbar to replace the one you have (do check paths as I've typed it here)

Code: Select all

TOTALCMD#BAR#DATA
utils\lst2mlt\lst2mlt.exe
/X:"utils\DirHash\DirHash.exe" /L:"%L"
c:\totalcmd\TOTALCMD.EXE,3

c:\totalcmd\

-1

[Dalai]

2Axis
When providing environment variables (with double percent signs) in the Parameters field, TC doesn't expand them, so it's the launched program's job to do so. Apparently, lst2mlt doesn't have such feature. Provide the parameters in the Command field instead and it should work.

Regards
Dalai

[petermad]

2Axis

Try this instead:

Command: "%commander_path%\utils\lst2mlt\lst2mlt.exe" /X:"%commander_path%\utils\DirHash\DirHash.exe"
Parameters: /L:"%L"

[Axis]

2Axis

Try this instead:

Command: "%commander_path%\utils\lst2mlt\lst2mlt.exe" /X:"%commander_path%\utils\DirHash\DirHash.exe"
Parameters: /L:"%L"

It works! (I guess for the explanation given by Dalai)
I have to mark these tips&tricks and hang to the wall

Thanks a lot to everyone

[solid]

AFIAK, TC doesn't support envars in parameters filed.

%C in parameters field passes the name of the file that is under the cursor.

So %COMMANDER_PATH% actually gets parsed as filename.extOMMANDER_PATH, supposing the cursor is on the filename.ext

[Horst.Epp]

AFIAK, TC doesn't support envars in parameters filed.

%C in parameters field passes the name of the file that is under the cursor.

So %COMMANDER_PATH% actually gets parsed as filename.extOMMANDER_PATH, supposing the cursor is on the filename.ext

You simply have to double the % in this case

[solid]

AFIAK, TC doesn't support envars in parameters filed.

%C in parameters field passes the name of the file that is under the cursor.

So %COMMANDER_PATH% actually gets parsed as filename.extOMMANDER_PATH, supposing the cursor is on the filename.ext

You simply have to double the % in this case

That will pass the literal string as parametar, it will not expand it.

[Dalai]

2solid
See my explanation above: https://www.ghisler.ch/board/viewtopic.php?p=402502#p402502

Regards
Dalai

[solid]

2solid
See my explanation above: https://www.ghisler.ch/board/viewtopic.php?p=402502#p402502

Regards
Dalai

The bottom line is that environmental variables are not supported in the parameters field. They are not expanding to their values.
We agree on this, don't we?

But I don't agree that we should expect from external programs to expand TC's internal variables, even if the programs are written for TC itself.

[Horst.Epp]

2solid
See my explanation above: https://www.ghisler.ch/board/viewtopic.php?p=402502#p402502

Regards
Dalai

The bottom line is that environmental variables are not supported in the parameters field. They are not expanding to their values.
We agree on this, don't we?

But I don't agree that we should expect from external programs to expand TC's internal variables, even if the programs are written for TC itself.

For any external program which is started from TC there is no difference between TC internal variables
and any other, they can all be expanded if the program does it at all.