cmd %PATH% ?

[brontosaurusrex]

Assuming my dir structure is

Code: Select all

totalcmd
    - totalcmd stuff
bat
    - myBatFile.bat

and when I start cmd.exe from one of the buttons, what are my chances that stuff in 'bat' dir will be visible as if on path?

As if

Code: Select all

set PATH=%PATH%;%COMMANDER_PATH%\..\bat\

was run. (edit: I guess I could just stick this to the top of each bat script)

In other words, I'd like NOT to use stuff like this in bat scripts

Code: Select all

%COMMANDER_PATH%\..\bat\SearchAndReplace

[wanderer]

Hi. You can add this path to system environment settings. Not in front of a pc now, so can't help any more atm.

[Stefan2]

Or just use
CD ..\bat\
in first line of your batch.

If need, you can also use PUSHD command to go forth and back in path history:
https://en.wikipedia.org/wiki/Pushd_and_popd


Or maybe you can use %COMMANDER_DRIVE%
https://www.ghisler.ch/wiki/index.php/Navigation





 

[wanderer]

Hi. You can add this path to system environment settings. Not in front of a pc now, so can't help any more atm.

If you really need this and Stefan's suggestion does not cover your needs, go to windows Search and type "edit environment variables for your account". In there, find the "PATH" environment variable and add your path. Be very careful though not to accidentally alter or delete any of the other paths because there may be unforeseen consequences.

[nsp]

If you want to have it in the path just add it in the path !

If you use TC from a single location then it is better to add your batch folder in the path system wide. I can advise you to use RapidEE for environment variable edition.

The variable commander_path is created once total commander is launched. So if you want to use it, you will have to set your path from TC process or sub processes. To do it from TC only once, IMO the best is to install AutoRun plugin and alter the PATH variable as you described using the ability to set env variable from autorun. The installation of autorun is a bit more complicated than usual content plugin. Just read and follow instructions of the help file.

[brontosaurusrex]

Thanks everyone, until the amount of batch files is small, I will live with adding

Code: Select all

set PATH=%PATH%;%COMMANDER_PATH%\..\bat\

on top of every script, will reevaluate when/if it gets more complicated.

[brontosaurusrex]

Or just use
CD ..\bat\
in first line of your batch.

Is that any different than the button that call the script with '%COMMANDER_PATH%\..\bat\' as 'start path'?

[Dalai]

I'm wondering what your goal is. Why do you need to working directory (start path) set? If you need to get the absolute directory of the currently running script, you can just use

Code: Select all

%~dp0

as reference.

Regards
Dalai

[brontosaurusrex]

@Dalai, thanks, noted (forgot about that one).

Goal is to have a folder structure ready for action that can be copy/pasted from machine to machine (perhaps even synced, perhaps synced via git). So the 'user' must only supply total commander to specific folder. Also minimum or better yet none changes to the windows itself.

The other part of the puzzle is to have start menu command or buttons which will start specific bash scripts inside wsl/Debian (not relevant to this thread).

[MVV]

Autorun plugin mentioned by nsp is a perfect place to add custom paths to TC's PATH variable that will be passed to all child processes.