redirect [Configuration] section

[ts4242]

i can redirect [Configuration] section by writng these setting under it
RedirectSection=1
AlternateUserIni=c:\redirect_test.ini

now when TC starts it read [Configuration] section from c:\redirect_test.ini not from Wincmd.ini

but according to help file this is not possible

AlternateUserIni=<somename> Will redirect storing of user-changeable sections to an alternate name, except for section [Configuration]. Useful for companies where wincmd.ini is write-protected.

All sections except for the following are redirected by default: Configuration, Layout, Packer, Confirmation, Extensions, Shortcuts, PackerPlugins, FileSystemPlugins, ListerPlugins, ContentPlugins

In each section except for [Configuration], an entry RedirectSection= will instruct Total Commander to redirect (or not) this section to another ini: Values: 0=no redirect, 1=redirect to AlternateUserIni=, <ininame> redirect to that specific ini

is this is a bug or am i missing something?

TC7/WinME

[StickyNomad]

2ts4242

First, when INI-redirection was introduced, redirecting the [configuration]-section wasn't supported, but was added later on.

[ts4242]

so Ghisler must update AlternateUserIni documentation

[StickyNomad]

You're right, it's indeed not mentioned yet there. That should be updated indeed.

[Clo]

2StickyNomad

Hello !

• Maybe do you remember that after the redirection for [Configuration] has been added, some annoying issues occured because that feature, and the Author regretted to have added it …

• So, I've the feeling that he's still a bit hesitant about to keep it definitely in the final 7.0 or not, and also that he is waiting for feedback here to decide on what to do…

• Whether he doesn't keep this, then the current Help is right

 VG
Claude
Clo

[StickyNomad]

2Clo

Thank you for this information

I must have missed the related issues somehow. I agree with you that we should wait then how Christian decides about that feature.

[sqa_wizard]

Excerpt from history .txt:

Code: Select all

22.03.06 Release Total Commander 7.0a1 (alpha test version 1)
...
28.02.06  Added: wincmd.ini: In each section except for [Configuration], an entry RedirectSection= will instruct tc to redirect(or not) this section to other ini: Values: 0=no redirect, 1=redirect to AlternateUserIni=, <ininame> redirect to that specific ini

but later on ...

17.05.06 Release Total Commander 7.0a5 (alpha test version 5)
17.05.06  Added: ini section [Configuration] can now also be redirected via RedirectSection= option. The options AlternateUserIni= and UseIniInProgramDir= will always be read from the non-redirected file, though

[Sheepdog]

The AlternateUserIni is meant to redirect the sections that should be edible for the users while the wincmd.ini is placed in a writeprotected area. So the user can't use the

[Configuration]
RedirectSection=1
AlternateUserIni=c:\redirect_test.ini

setting to get access to the restricted Sections.

But as StickyNomad mentioned: The redirection of the CONFIGURATION section has been added later on - specailly requested by a particular Beta Tester - for the following purpose:

Sometimes it is useful to have different wincmd.ini files for different projects e.g. with other searches, COlor-settings, [LEfttabs/Righttabs] sections etc. But the [Configuration] settings should be all the same. And a change in these Settings - should affect all those different ini-files. Otherwise you would have to edit each of those different ini-files as soon as you'll have changed a setting. with

[Configuration]
RedirectSection=c:\totalcmd\commonConfig.ini

you can achieve that all different projet-inis refer to one Configuration- section while the other sections are referred only from this particular project.

But you are right: The help should be updated (I am convinced that this feature will survive till the final version is published )

sheepdog

[petermad]

The punctuation and syntax in history.txt of:

Code: Select all

Values: 0=no redirect, 1=redirect to AlternateUserIni=, <ininame> redirect to that specific ini

should be changed to:

Code: Select all

Values: 0=no redirect, 1=redirect to AlternateUserIni, <ininame>=redirect to that specific ini

As it is now the last part doesn't make sense.

And I agree with Sheepdog, this feature must NOT be taken away again.

[Lefteous]

The RedirectSection setting has one big disadvantage. It breaks compatibility will all plug-ins who read settings from Wincmd.ini. This doesn't work anymore if the user has redirected a section which is required by the plug-in.
All these plug-ins doesn't work properly anymore. They have to add RedirectSection support.
I thought compatibility is the number one priority


Beside that is there any documentation which path expressions are allowed for RedirectSection? It's well known that just file names or relative path expressions are not supported by path settings in Wincmd.ini. For RedirectSection this doesn't seem to be the case which is quite inconsistent. In addition it makes handling RedirectSection properly even more difficult for plug-in authors.

[ghisler(Author)]

In fact plugins have nothing to look for in wincmd.ini! This isn't part of any official API, so if a plugin does it, the plugin user has to live with it, and either not use the redirect option, or update the plugin.

[Lefteous]

2ghisler(Author)
So why did you add %COMMANDER_INI%

[ghisler(Author)]

This was added for ini file editors for TC. These programs are usually updated to work with the latest ini file options anyway, so the authors can add support for redirection too.

[Lefteous]

2ghisler(Author)
Anyway would you please reply to this:

Beside that is there any documentation which path expressions are allowed for RedirectSection? It's well known that just file names or relative path expressions are not supported by path settings in Wincmd.ini. For RedirectSection this doesn't seem to be the case which is quite inconsistent.

[Clo]

2Lefteous

Hello Christian!

• I agree with your remarks. In example : not only plugins have issues with redirections… Tools have too !

- Just try to use TC Plugman with plugins sections redirected into covering INIs…

 VG
Claude
Clo