It is definitely not a bug. When the template ends with a variable name, the variable contains the "remainder of the string" beginning with the first character after the last ASSIGNMENT, which includes the space(s) between the last assignment and the start of the next word. The interpreter doesn't know that the last variable is a "word." I just totally missed that I had somehow forgotten to put a trailing " . " which is what the interpreter needs to turn the last-variable into a "word." I knew that,...
Incorrect value of .FILE
Error in SYNTAX trapping
I should have checked this first. The reason I've never seen it before is that I always put a trailing placeholder at the end of the template, and didn't this time. If I use parse var _z.i . . . . fname . then fname does not have a leading space. I still think it should never have a leading space, but at least now I know how to avoid the problem.
Incorrect result from basic PARSE
Additional info. Since double-clicking filenames with .rx extensions works, I tried '__txt2html__.rx' 'x' and it worked fine.
Installer issue with Windows 10
The utcoffset exec does give the correct results, so thank you! But here's a question....