Temp directory Focus

[Boofo]

Is there a way to focus em_temp in the left pane using a button in the button bar? It opens up in whatever pane is focused right now. Thanks in advance.

[Hacker]

Using command line parameters should work.

HTH
Roman

[Boofo]

I tried using the command line parameters and couldn't get it to work right. I am using em_temp for the Command option right now.

[Sombra]

PLEASE, read => F1 > Section 4. a

Command: %COMMANDER_PATH%\TOTALCMD.EXE /o /l=%temp%

[Boofo]

I tried doing it exactly that way and all it does it make the left pane mimic the right pane as to what directory shows up. And, believe it or not, I did read that first.

[Boofo]

Ok, I got it working. I was using %COMMANDER_PATH%\TOTALCMD.EXE for the command and /O /T /L=%temp% for the parameters. I didn't know you had to put it all in the command line. Why doesn't it work the original way I did it?

[karlchen]

Hi.

On WinXP the "%temp%" folder name will enclose space characters. Therefore, it may be advisible to use

Code: Select all

"%COMMANDER_PATH%\TOTALCMD.EXE" /o /l="%temp%" 

instead.
On my Vista system, both commandlines work as expected.

Code: Select all

%COMMANDER_PATH%\TOTALCMD.EXE /o /l=%temp%
"%COMMANDER_PATH%\TOTALCMD.EXE" /o /l="%temp%"

I.e. the current T.C. instance will be reloaded and the left hand panel will have the focus and the current folder will be "%temp%". Neither expanded foldernames of %COMMANDER_PATH% or of %TEMP% encloses any space characters here.

<Added>
Confirmed. I put everything into the commandline field. The parameter field will not expand environment variables, i.e. %TEMP%. This is a known limitation, as far as I know. T.C. internal variables like %P %N %T %M %S %L might collide with environment variables having the same names.
</Added>

Karl

[Boofo]

I am using this as a button in the button bar. It only works if I put the whole line in the Command option. If I split it up and add the parameters in the Parameters option, it no longer works. Shouldn't it work both ways?

Doesn't %COMMANDER_PATH% take the spaces into account already?

EDIT: My message beat your edit. Thanks for explaining that.

But it still is weird how it works that way.

[HolgerK]

<Added>
Confirmed. I put everything into the commandline field. The parameter field will not expand environment variables, i.e. %TEMP%. This is a known limitation, as far as I know. T.C. internal variables like %P %N %T %M %S %L might collide with environment variables having the same names.
</Added>

Workaround: use %% instead of %

Code: Select all

TOTALCMD#BAR#DATA
%COMMANDER_PATH%\TOTALCMD.EXE
/o /l="%%temp%%"
%COMMANDER_PATH%\TOTALCMD.EXE



-1

Regards
Holger

[Hacker]

Workaround: use %% instead of %

Exactly. There is %T (TC's internal variable for target path) in %Temp%.

Roman

[Boofo]

2Hacker,
But shouldn't it look at the whole variable? (Like what is between the % signs.)

Thank guys. It works with the double %. Did I miss that somewhere in the chm file, by chance? If I did, I apologize for not knowing this.

[Hacker]

Boofo,

But shouldn't it look at the whole variable? (Like what is between the % signs.)

Well, the variable that TC encounters first is %T, and it does not check if you might have perhaps meant some other combination of %'s to mean something else. So TC just expands %TEMP% to "c:\target\panel\dir\emp" and as it cannot find the "emp" subdir it goes one dir higher (which matches the %T dir). Just for fun, you can try creating an "emp" subdir in the target panel and see if the source panel goes there after executing the %TEMP% command.

Roman

[Boofo]

I tried the "just for fun" experiment and you are right. It goes to the target "emp" directory with %temp%. It makes sense but I still think the parameters should be read wholly.

[HolgerK]

But shouldn't it look at the whole variable? (Like what is between the % signs.)

How should then a parameter like this

%T%N

interpreted, if at the same time an environment variable %T% is defined?

Regards
Holger

[Boofo]

You have a point there. I guess the double %% is the best way around this scenario. Thanks for coming up with that, sir.