Total Commander

Subj.
If i try to run new OPENBAR cmd from TC commandline, it doesn't work (file not found message appear). But it work, when i try to run it from menu or toolbar button.

Exept for CD and cm_list it is the same thing with the other commands that takes parameters: OPENTABS, APPENDTABS, FTPOPEN, LOADSEARCH and SYNCOPEN.

OPENBAR is not supported on the command line, just like the other commands with parameters. Currently it's not planned to change that.

Wouldn't it be great if %A would be expanded for internal command with parameters as suggested here?
http://www.ghisler.ch/board/viewtopic.php?t=12184

[mod]Moved to TC 7 beta discussion forum.

Hacker (Moderator)[/mod]

ghisler(Author) wrote:OPENBAR is not supported on the command line, just like the other commands with parameters. Currently it's not planned to change that.

But...........

If you do a user command "em_LoadBarThatMrGhislerDoNotWantIUseFromTheCommandLine" or a shorter one like "em_LoadBar"
command: OPENBAR
parameter: %A

then, you can tip in the command line :
em_LoadBar c:\totalcmd\profiles\bars\MMedia.bar

And then ... the bar show up ! alleluia

( Please Mr Ghisler can you unify command as if it accepts parameter, it accepts in the same way :
From the menu. (Done)
During user command or alias definition. (Done)
From the command line. (Almost done with dirty trick)
Externally using windows send-message ! (instead of populating the command line !, very dirty trick)

This would be so kind !!!!!

2nsp
Wow - I didn't know that! didn't find anything in the history. It seems %A must be specified explicitely. It doesn't work if the parameters field is just empty.

Arrow From the command line. (Almost done with dirty trick)
Arrow Externally using windows send-message ! (instead of populating the command line !, very dirty trick)

What's so dirty about these two? User commands are used in all cases. Just typing is even simpler then typing openbar <my bar>.

Lefteous wrote: It doesn't work if the parameters field is just empty.

You are right ! I discover it just because i never let parameter empty if i want to use it via cmdline !

Lefteous wrote: What's so dirty about these two?

Personally i enjoy it and, i can most of the time do my stuff working with Powerpro, some prefers AHK ...

1) You have to use a (additional) usercmd to make the std cmd work as you want !

This is a small trick that make TC not so user friendly to new/occasional users.

2) I do not understand why some command works from the menu or the cmd line and not using external automation tools (sendmessage) ...

3) we have wonderful %f %F %L ..... pseudo variable not available in cmdline and !

So i create temporary em_cmd in usercmd.ini in order to launch them externally ! ( It works like a charm ! )

4) cm_list do not accept parameters from cmd line ... so you call the external lister.exe .....


These are tricks, i use and share with people i convinced to use TC.

Nice, you found a way to do it which wasn't even planned.