Behavior of: %COMMANDER_INI%\..

[krasusczak]

Hello all,

I was trying to modify a little extended English menu ini: wcmd_win7x86_1_eng.ini for opening a new instance of TC from my special config location but I found something strange

So here is what I'm trying to use there:

[em_ext_newcommander1]
cmd=*%COMMANDER_EXE% /N /P /A /i="%COMMANDER_INI%" /f="%COMMANDER_INI%\..\wcx_ftp.ini"
param=%Z%X %P%N* %T%M*
menu=Open New Instance of Total Commander as Administrator
button=%COMMANDER_EXE%

I have my configuration dir with all my cfg's here: c:\Program Files (x86)\totalcmd\config\

But new instance started via this has this values:

Settings files:
c:\Program Files (x86)\totalcmd\config\wincmd.ini
c:\Program Files (x86)\totalcmd\config\wincmd.ini\..\wcx_ftp.ini

It shouldn't have??:
c:\Program Files (x86)\totalcmd\config\wcx_ftp.ini

I found many topics that if I will use %COMMANDER_INI%\.. it should be resolved as main config directory, am I missing something here?

Any advice appreciated, thanks!

[Horst.Epp]

%COMMANDER_INI% is not a directory.
It's just the full path of the current ini file.
You can use %COMMANDER_PATH% as base for your other ini files.

[petermad]

2krasusczak

I tested your scenario. event though "About Total Commander" shows: c:\Program Files (x86)\totalcmd\config\wincmd.ini\..\wcx_ftp.ini it actually works - try and oprn the "Connect to FTP server" - it will open c:\Program Files (x86)\totalcmd\config\wcx_ftp.ini and changes are written to c:\Program Files (x86)\totalcmd\config\wcx_ftp.ini - so it must be a bug in the "About Total Commander" dialog.

Also try - after you have opened the New Instance of Total Commander as Administrator - to run notepad "%COMMANDER_INI%\..\wcx_ftp.ini" it will open c:\Program Files (x86)\totalcmd\config\wcx_ftp.ini

[white]

I tested your scenario. event though "About Total Commander" shows: c:\Program Files (x86)\totalcmd\config\wincmd.ini\..\wcx_ftp.ini it actually works - try and oprn the "Connect to FTP server" - it will open c:\Program Files (x86)\totalcmd\config\wcx_ftp.ini and changes are written to c:\Program Files (x86)\totalcmd\config\wcx_ftp.ini - so it must be a bug in the "About Total Commander" dialog.

It's a feature of Windows that relative paths like this work. It has nothing to do with TC. Why would you call it a bug just because canonicalization is not done?

[JOUBE]

It's always the same: [Tc11] Suggestion: COMMANDER_INI_PATH

[petermad]

2white

Why would you call it a bug

OK - a missing feature then.

[krasusczak]

2petermad
Good catch!, when I was testing this by mistake my test file had only old connections without any ftp config so I didn't se this haha

It looks for me kind of visual bug/enhancement, which maybe could be changed at least for About window?
2ghisler(Author): what do you think about this?

[petermad]

what do you think about this

I think that as long as TC does not have a %COMMANDER_INI_PATH% variable ( viewtopic.php?t=78954 ) it would be pertinent that TC would dessolve %COMMANDER_INi%\..\ correctly in the About dialog.

[petermad]

Moderator message from: petermad » 2023-11-11, 19:56 UTC

Moved 8 posts to "[Tc11] Suggestion: COMMANDER_INI_PATH" in "TC suggestions (English)"

[Profane0360]

My two cents here, if I may. I have a similar issue myself.

I start TC with my own CMD file, where I set up the path with a few things that I need inside TC, as, for instance, LaTeX, Perl, C, Java paths. Then I do a start with the complete TC command line pointing to the two INI files and the drives that I want visible as I start.

My alternative to this CMD would be a LNK file with the INI files parameters and the Autorun plugin. But I prefer the CMD file.

With a CMD file I am actually tempted to have my own set of predefined variables, pointing to all the relevant folders. They can be used consistently in the TC universe, as they are created before starting TC and visible inside TC.

%TCMD_ROOT%
%TCMD_BIN%
%TCMD_INI%
%TCMD_PLUGINS%
%TCMD_TOOLS%

Why would this approach be a bad idea? What disadvantages does it have?

[Stefan2]

%TCMD_ROOT%
%TCMD_BIN%
%TCMD_INI%
%TCMD_PLUGINS%
%TCMD_TOOLS%

Why would this approach be a bad idea? What disadvantages does it have?

Maybe because the storage space for Env Vars is limited.
So we all should only take as much as we really need.

The user can take much more if he want on a single system, but the developer
must keep in mind that all applications have to share the same storage space.

Also see "the maximum length of an environment variable" at https://devblogs.microsoft.com/oldnewthing/20100203-00/?p=15083


 

[Profane0360]

The user can take much more if he want on a single system, but the developer must keep in mind that all applications have to share the same storage space.

Yes, indeed. This is exactly my point. Instead of having Mr Ghisler, the developer, preset all these variables and add more, I, the user, may organize my own set of variables on my own system the way I see fit. Thank you indeed for your input.

[krasusczak]

From my perspective it would be ok to just fix this graphical "inconvenience" without playing with env var changes