relative paths don't work for me on linux when using 'include' in scripts, while ironically they seem to work fine on Windows. Here's the example: <script1> # this script 'scriptinlevel2.inp' resides in $HOME/gretlpathtest/level2 include ../scriptingretlpathtest.inp print "hello" </script1> <script2> # this script 'scriptingretlpathtest.inp' resides in $HOME/gretlpathtest function pathtest(int yo) print "inside function" end function </script2> Now when I run the first script on linux, an error window pops up "no such file or directory".

Allin Cottrell schrieb: > Re. the issue raied by Sven in > > http://lists.wfu.edu/pipermail/gretl-devel/2009-August/002060.html > > I've now tried to make path-searching a little more clever. If a > script is successfully opened, gretl should be able to find > other files referenced in that script that are specified by > relative paths such as "../foo", where the "relativity" centers > on the directory containing the previously opened script. > This is much appreciated!

On Tue, 18 Aug 2009, Sven Schreiber wrote: > relative paths don't work for me on linux when using 'include' in > scripts, while ironically they seem to work fine on Windows. > > Here's the example: > > <script1> > # this script 'scriptinlevel2.inp' resides in $HOME/gretlpathtest/level2 > > > print "hello" > </script1> > > <script2> > # this script 'scriptingretlpathtest.inp' resides in $HOME/gretlpathtest > > function pathtest(int yo) > print "inside function" > end function > </script2> > > Now when I run the first script on linux, an error window pops up "no > such file or directory". Where are you running the first script from? I'm not sure why you would expect it to work (to include the second script) unless the CWD was $HOME/gretlpathtest/level2 (it does work in that case).

include ../scriptingretlpathtest.inp