Questions about RedirectSection for Hotlist

[JnLLnd]

Hi,

I know I could find answers to my questions by doing try and error. But if one could save me some time and answer these questions, I would appreciate.

Ghisler wrote here some time ago that:

RedirectSection only works in wincmd.ini, not in the redirected files

Is it still the case in current version, especially for the [DirMenu] section? I understand RedirectSection cannot be recursive?

If the redirected filename does not include a path, does the redirected file must be in the same folder as wincmd.ini? Or same as the TC working directory (in AppData)? Or same TC executable file?

I read that env variables are supported. Are relative path also supported? For example, "..\this_or_that\hotlist.ini".

Can WinCmd.ini include a mix of items + redirections, for example:

[DirMenu]
menu1=CONTROL &PANEL
cmd1=cm_OpenControls
RedirectSection=hotlist.ini
menu2=&DESKTOP
cmd2=cm_OpenDesktop
...

If yes, would items in hotlist.ini must start over at #1 (menu1= ...)?

Finally, I assume the data format in redirected files is the same as in WinCmd.ini. Correct?

I need to know this to improve TC support in Quick Access Popup following a TC user new to QAP. Currently, Hotlist items can be shown in QAP menu but only for items saved directly in WinCmd.ini. I want QAP to also support redirection.

Thanks for your help,

Jean

[MVV]

I understand RedirectSection cannot be recursive?

Yes, only wincmd.ini can redirect, redirection is not recursive.

If the redirected filename does not include a path, does the redirected file must be in the same folder as wincmd.ini?

Redirected file w/o path must be near wincmd.ini, it is easy to check using TOTALCMD.exe /I=file.ini.

I read that env variables are supported. Are relative path also supported? For example, "..\this_or_that\hotlist.ini".

It may also be checked easilly, and it seems that relative paths are not supported, though you can use something like %COMMANDER_INI%\..\..\this_or_that\hotlist.ini as a workaround.

Can WinCmd.ini include a mix of items + redirections, for example:

No, only entire section may be redirected, if section is redirected, its contents in wincmd.ini is ignored.

Finally, I assume the data format in redirected files is the same as in WinCmd.ini. Correct?

Yes, you can simply cut section from wincmd.ini.

[JnLLnd]

Great answers, MVV. Thanks.

I'm ready with this to complete hotlist parsing in QAP. I will let you know when this is done.

Jean

[batchman61]

Hi,

simple workaround is to configure WinCmd.ini location in QAP to the ini file containing the redirected [DirMenu] section. Works without any issues here.

[JnLLnd]

Yes. Why not! Thanks batchman61

[MVV]

JnLLnd,
If you support RedirectSection parameter in [DirMenu] section, you should also support AlternateUserIni parameter in [Configuration] section.

[JnLLnd]

JnLLnd,
If you support RedirectSection parameter in [DirMenu] section, you should also support AlternateUserIni parameter in [Configuration] section.

Yes. Good point, got it. Thanks.

AlternateUserIni=<somename.ini>
If present, it will redirect storing of all user-changeable sections to an alternate ini file (in this example, somename.ini), except for the following sections: [Configuration], [Layout], [Packer], [Confirmation], [Extensions], [Associations], [Shortcuts], [ShortcutsWin], [PackerPlugins], [FileSystemPlugins], [ListerPlugins], [ContentPlugins]. These sections can be redirected individually, though:
In each section, an entry RedirectSection= can be added to change the default behaviour. It will allow to redirect (or not) this section to another ini file: Possible values:
0: no redirect
1: redirect to ini file defined via AlternateUserIni=<alternate ini file.ini>
<ininame.ini>: redirect to that specific ini

[ghisler(Author)]

Please be aware that wincmd.ini and the redirected ini don't need to use the same encoding. My wincmd.ini is ANSI, while my redirected ini is Unicode UTF-16. Only two two encodings are supported by Windows ini functions.