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.
missing executable name Lst2Str issue -
Moderators: white, Hacker, petermad, Stefan2
-
cookietran
- New Member
- Posts: 1
- Joined: 2020-08-03, 10:03 UTC
-
gdpr deleted 6
- Power Member
- Posts: 872
- Joined: 2013-09-04, 14:07 UTC
Re: missing executable name Lst2Str issue -
I don't exactly know what you are using Lst2Str for (it is rather old, from the year 2005).
But there is a good chance that you can do without Lst2Str. For example, if you are using it in conjuction with a toolbar button in TC, you can directly pass the selected files as command line parameters to the program you want to execute. To do this, use the %P%S parameter in the Parameters field of the toolbar button...
But there is a good chance that you can do without Lst2Str. For example, if you are using it in conjuction with a toolbar button in TC, you can directly pass the selected files as command line parameters to the program you want to execute. To do this, use the %P%S parameter in the Parameters field of the toolbar button...