Paths with spaces not being handled properly by codes

This was just a part of several buttons/context menu items I was creating - and I was surprised that it did not work - thinking I had done something very similar in an earlier release (but never kept as part of my permanent config):

@set var = "{Rs|Specify output TXT filename|{s}{s|nopath|noterm}}.txt" dopusrt /ArgsMsgBox {$var}
...when run in a path with spaces only returns the {s} part of the expected string. So in a path like "D:\my\My Media" this code only returns "D:\my\My Media.txt" instead of adding the {s|nopath|noterm} piece at the end in order to get the expected "D:\my\My Media\My Media.txt" output as the result of this code...

You wouldn't want the quotes to be included around the {s} and/or {s|nopath|noterm} anyway, since then they'd appear in the dialog's default text, and get included inside of the already-quoted variable.

@nofilenamequoting @set var = "{Rs|Specify output TXT filename|{s}{s|nopath|noterm}}.txt" dopusrt /ArgsMsgBox {$var}

Ah, I hadn't mentioned trying to disable the quotes such as you've done - because I could have sworn I tried that and it still didn't work. Hmmm... anyways, I've gone and done what you don't like us to do - and withheld what I'm actually trying to accomplish and posted this code as just an example.

The problem with disabling the auto quoting is that it clobbers the quoting that happens when I try to use {F} as a code to pass multiple files an external tool. I was basically trying to do something like:

c:\tools\utility.exe "{Rs|Specify output TXT filename|{s}{s|nopath|noterm}}.txt" {F}

Where the tool wants what Opus normally does with multiple files selected - by quoting each file separately. Having tried @nofilenamequoting and thinking it had failed (?) made me post this. Not sure what went wrong in my test, but now that I see it was indeed the multiple quotes causing the problem - I suppose I'll come up with another way to provide the output filename I want. Thanks.

SIDE NOTE: hardly a burning priority, but for granularity of control - is there any potential to consider a generic noquote control code modifier for all control codes that could disable quoting only in the instance(s) of the control code where you might use such a modifier?