Actually, Charles, no; although it really wouldn't make any practical difference in this case. "%$" is "the complete command tail, modified by SHIFT", whereas "%*" is "the complete command tail, unmodified by SHIFT", and since I am not (never will) be doing any "SHIFT" commands in this "application", it really doesn't matter in this case. (And frankly, that being the case, I have a slight bias for "%*"', I use "%$" only when I am explicitly doing shifts.)

- Dan

P. S. Thank you, Charles!!! You were correct!!!! I just did that "experiment" after originally hitting the "Save Changes" button on this; I thought "Just for the heck of let's see what this does...", and it does exactly what I would want it do. But do you know why "%*" doesn't work???

The Help page for "Function" says that "%$" does what you want, but doesn't mention "%*". Since the latter isn't mentioned, your function is presumably just returning "%*", regardless of the argument. So, the result you get is the same as doing "echo %*".

You are, of course, right as always, David. (My inability to see is, as oft mentioned before, a real handicap.) However, they not only do they not behave the way I would expect from the documentation, the "results" can actually be far worse (more on that at the bottom of this). So, to "illustrate" these things, here is a TCC "log".

And here is the end of the whole thing, because at this point TCC just crashed. (Since I knew it was going to crash from a previous run-through, I saved this to a file before I issued the above command.)

What's kind of remarkable to me is that nobody (apparently even you) has "noticed" this behavior before.