On Sun, 14 Mar 2010, Sven Schreiber wrote:
Sven Schreiber schrieb:
> Allin Cottrell schrieb:
>
>> I've just experimented and I can't reproduce the problem you
>> describe. That is:
>>
>> * In gretl GUI, open script from ad hoc location (not working
>> directory, not shell PWD) via File menu. This script starts with
>> a command to open a datafile with no explicit path given, and the
>> datafile in question is in the same ad hoc location.
>>
>> * Run script; datafile is found OK as advertised.
>>
>> * Make changes to script and save it. Re-run script. Datafile is
>> still found.
>>
>> I don't doubt that you're seeing what you're seeing, but could you
>> give a little more detail? What does the script do, for instance?
Ok, it seems pretty clear now:
The essential structure of the script is:
open file_in_same_directory.gdt
include ../script_in_upperlevel_dir.inp
And the "jump" to ../ seems to confuse the path-finding apparatus.
It's rather that doing "include" has switched the "current" path
to the one where the second .inp file was found. Bug or feature?
For the present I've modified the behavior so that "include"
doesn't alter the "current" path.
Allin