Done SHORTCUT command should accept unexpanded environment variables.

Apr 13, 2010
298
7
60
The Hague
The current implementation tries to validate the arguments. When the relevant arguments contain unexpanded envars the validation fails. Either the %envars% are not interpreted correctly (expanded) by the validation or they are not (yet) defined which in itself is perfectly reasonable; they *must* be defined or have a valid value only at run-time, e.g. when the shortcut is clicked. Whatever causes the validation to (incorrectly) fail, TC tries to fix the problem by inserting reasonable defaults for the parts it misses. If the unexpaned string was well formed before validation, after these additions it probably won't be.

I would like to suggest that unexpanded environment variables are allowed by the validation and no corrections are attempted if present.