Standalone Lister32 known issues (so far)

[Helix751]

I have been trying LISTER32 for years and havund scattered info on its behavior since it's not mntained at all.

I know totalcmd's /S=L command line invokes Internal Lister and does the job pretty well, but for anyone seeking to configure the external LISTER32 version, here are my findings:

1. Lister32 can actually read wincmd.ini file, BUT:
   1. It must reside in totalcmd's program folder; or
   2. It has to be referenced absolutely, eg. c:\totalcmd\lister.exe /i="%APPDATA%\GHISLER\wincmd.ini"
   3. Lister32 doesn't natively read an ini file inside the user's profile dir.
2. Lister32 doesn't recognize the %COMMANDER_PATH% variable, so if plugins are installed and referenced using this var, they will neither be recognized nor used.
3. Any lister plugin that references a file or executable using the %COMMANDER_PATH% variable will fail with errors (e. slister - Sumatra PDF lister plugin). The variable MUST be expanded to the actual path to work.

[petermad]

2Helix751

1. Lister32 doesn't recognize the %COMMANDER_PATH% variable, so if plugins are installed and referenced using this var, they will neither be recognized nor used.

2. Any lister plugin that references a file or executable using the %COMMANDER_PATH% variable will fail with errors (e. slister - Sumatra PDF lister plugin). The variable MUST be expanded to the actual path to work.

I find that %COMMANDER_PATH% is resognized by Lister.exe - but of course Lister.exe has to started from TC, otherwise the %COMMANDER_PATH% variable will not be set if TC is not running.

[Helix751]

2Helix751

1. Lister32 doesn't recognize the %COMMANDER_PATH% variable, so if plugins are installed and referenced using this var, they will neither be recognized nor used.

2. Any lister plugin that references a file or executable using the %COMMANDER_PATH% variable will fail with errors (e. slister - Sumatra PDF lister plugin). The variable MUST be expanded to the actual path to work.

I find that %COMMANDER_PATH% is resognized by Lister.exe - but of course Lister.exe has to started from TC, otherwise the %COMMANDER_PATH% variable will not be set if TC is not running.

That's the key issue. It depends on Totalcmd but as a standalone program, it inherently doesn't recognize the %COMMANDER_PATH% variable. For instance, when launching it from Explorer's shell.

[petermad]

it inherently doesn't recognize the %COMMANDER_PATH% variabl

There is nothing to recognize - if TC is not running there is no %COMMANDER_PATH% variable - unless you set it yourself manually before starting Lister or TC.