Am 22.12.2007 00:46, Sven Schreiber schrieb:
Am 21.12.2007 23:27, Allin Cottrell schrieb:
> Do you mean, that if a script references another file given as a
plain
> (non-dot) relative path, gretl will look for the latter in the same
> place the script was found? If so, this is the case for open/append
> and run/include. For example, if I do
>
> gretlcli -b /some/odd/place/foo.inp
>
> and foo.inp says "open baz.gdt", then we try looking for baz.gdt in
> /some/odd/place. There's an internal variable "currdir" which is
> set/reset each time a script is opened, and this directory is
> prepended to the search path.
>
Hm, ok, though my question arises from experiences where I thought that
wouldn't work. I'll report it as a bug eventually when I come across
something reproducible and clearcut.
Maybe it was a problem with 1.6.5, my co-author had such a problem
shortly before 1.7.0 was released. But with the current snapshot
everything seems fine in this respect.
-sven