Lst2Str issue - missing executable name

[jdmarch]

I believe that the very useful add-on, LST2STR, has a bug. When a program is invoked from the command line, and reads its complete command line string, that strong normally begins with the name of the executable, followed by the parameters/filenames. Instead, when LST2STR invokes a program, and that program reads its command line, the string begins with a space, followed by the parameters/filenames. The executable name is missing.

The reason that this is a problem is that some utilities parse the command line, expecting the first non-blank token to be the executable name, the second non-blank token to be the first parameter, etc. So they interpret the parameters incorrectly. To use such a utility with LST2STR requires a workaround using /S: to insert a dummy first parameter.

Thanks!
Jonathan