How much does TC go in deep for RedirectSection

[HBB]

Hello friends,

I am just trying to learn how RedirectSection is used.
RedirectSection feature also seems to be excellent for using TC over LAN for multi-user usage.

I have a problem. Let me explain it in an example as follows :

In wincmd.ini :

[Configuration]
AlternateUserIni=wincmd_User.ini
:

In wincmd_user.ini :

:
[LeftHistory]
RedirectSection=wincmd_User_History.ini
:

Even if there is no section [LeftHistory] in wincmd.ini :
- TC always try to write into wincmd.ini
- TC does not write into wincmd_User_History.ini

According to help in TC, when AlternateUserIni=<somename.ini> is defined, TC tries to write the settings into <somename.ini> if there is no related section in wincmd.ini

I expected that TC write the left history into the section [LeftHistory] in wincmd_User_History.ini. But not...

Does TC support one level depth in redirection?

Best wishes.

[MVV]

Maybe TC doesn't support this. Why not just to put into wincmd.ini section LeftHistory?

[LeftHistory]
RedirectSection=wincmd_User_History.ini

[HBB]

MVV, Thank you for reply

Why not just to put into wincmd.ini section LeftHistory?

In our company, we are using TC over server. By RedirectSection, users get main sections from TC (as read only) and write their own spesific sections into their ini files.

Since the users are not so familier to TC, I always add and control plugins by myself.

Edited >>> you are right, currently, I do it as you suggest.

Regards

[ghisler(Author)]

RedirectSection only works in wincmd.ini, not in the redirected files - this could lead to infinite loops where one ini file could point to another, and that would point back to the first. So you can put
[LeftHistory]
RedirectSection=wincmd_User_History.ini
in the main wincmd.ini to override the setting in AlternateUserIni for just that section.

[HBB]

To Ghisler,

Thank you for the clarification.

Regards