Inconsistent presentation of quotation marks in parameters
Posted: 17.04.2019, 16:32
FreeCommander presents quotation marks in parameters if the path it represents contains a space.
But it does not if the path does not.
This makes sense, but in many use cases produces unexpected and undesired results.
For example when using FastCopy as a copy program, FastCopy requires a trailing slash "\" on the path name to operate correctly.
If you represent this as "%InactiveDir%\" then it WORKS if the path does not contain space:
("c:\mydir\mydir2\" is produced)
However it DOES NOT work if it does contain a space:
(""c:\my dir\my dir2"\" is produced)
If FC did not produce quotation marks in parameters in any circumstance, then the behaviour would be predictable and the user could enter the quotations wherever they needed them.
(To obtain backward compatibility with existing users is may be better to add new parameter names that NEVER include a quote? For example %InactiveDirNoQuote% - then "%InactiveDirNoQuote%\Remaining path" would work).
Thanks for a great free product. FC is a lifesaver !!!
But it does not if the path does not.
This makes sense, but in many use cases produces unexpected and undesired results.
For example when using FastCopy as a copy program, FastCopy requires a trailing slash "\" on the path name to operate correctly.
If you represent this as "%InactiveDir%\" then it WORKS if the path does not contain space:
("c:\mydir\mydir2\" is produced)
However it DOES NOT work if it does contain a space:
(""c:\my dir\my dir2"\" is produced)
If FC did not produce quotation marks in parameters in any circumstance, then the behaviour would be predictable and the user could enter the quotations wherever they needed them.
(To obtain backward compatibility with existing users is may be better to add new parameter names that NEVER include a quote? For example %InactiveDirNoQuote% - then "%InactiveDirNoQuote%\Remaining path" would work).
Thanks for a great free product. FC is a lifesaver !!!