Re: [Gretl-devel] open path bug
Allin Cottrell schrieb:
On Sat, 13 Mar 2010, Sven Schreiber wrote:
> Sven Schreiber schrieb:
>> I have a script and a workfile in the same directory (and that directory
>> is not the CWD or dotdir or anything). The script starts with the open
>> command:
>>
>> open ea16_96m1_sven18feb10.gdt --quiet
>>
>> and after starting gretl everything works fine.
>> However, when I modify the script a little bit, save it, and then
>> execute it again, I get an error:
>>
>> ? open ea16_96m1_sven18feb10.gdt --quiet
>>
>> Fehler bei Skriptausführung: Stopp
>>
>> Restarting gretl cures the (apparently reproducible) issue.
> actually it seems that it's enough to reload (close/open) the script
> file to work around this issue
I'm not convinced this is a bug. If you want to ensure that files
in a particular (ad hoc) directory are found, the best way is to
make that your PWD and choose the option to make your gretl
working directory respect the PWD on start-up.
I was doubting it myself, but then I found this in the command ref:
"When a command script contains an instruction to open a data le, the
search order for the data le is
as stated above, except that the directory containing the script is also
searched, immediately after trying
to nd the data le \as is"."
I think this intended behavior actually makes sense, because it feels
natural that files in the very same directory should be found; at least
that's common behavior for most programs I think.
thanks,
sven