this command won't work if you add spaces in front of it
Sorry, h7se, I have to disappoint you.
This is not a bug to be fixed.
It is only an issue to be explained.
When processing a single script command line, WB does:
- Split the command line into an array of arguments. Split delimiter is the comma
(that is the reason, why inside an argument a comma must be replaced by #$c)
- take the first argument (completely, including leading and trailing white spaces) to dispatch to the corresponding routine.
If in the dispatch table no match is found, the complete line is treated as comment: No log, no error message, just: "I do nothing"
Maybe this behaviour can be changed. But currently it is 'WB reality'.
I'm already familar with this: If in my log a line is missing, I look for: 'What did I spell wrong in the command name'