Is Obey's handling of paths bugged?

During the last MUG meeting it was pointed out to me that a StrongED related directory was being opened with a path as its title. Because of this the directory could not be written to.

After some digging, I found out that this was caused by the use of the Obey command. Replaced Obey with Run and Obey$Dir became a directory (ie a canonicalised filename).

In the source for the Obey module there is the following comment:

;avoid the exceedingly naff method of XOS_CLI to *Set Obey$Dir, since it
;is needlessly slow (use XOS_SetVarVal instead)

So, Obey’s behaviour is deliberate but is it right? Shouldn’t Obey$Dir always be set in the same way?

I think it should hence putting this in the Bugs section but I’m curious to hear what others think.

Do you have a Repro?

I’m not 100% clear on what you’ve descripted but reading between the lines, it sounds similar to what happens when parsing the environment string and getting the path to the launching command instead of the parameter.

I’ve placed a quick Repro on the StrongED website.

Hopefully this will make clear what I’m referring to.

Edit: fixed link to Repro zip