> > Actually my cheers were too early. It doesn't work after a restart of > > gretl, so I guess I changed the workingdir (or similar) by chance > > before, which made me think it works. > > Wouldn't it be an option for you to set the workdir (CWD) accordingly in the > first place? > > Apart from that, I managed to dig up an old thread from the devel list, see > http://lists.wfu.edu/pipermail/gretl-devel/2009-August/002063.html > -- OMG, more than eight years ago... > > "gretl should be able to find ... relative paths such as "../foo" " > > If it doesn't work, it would be interesting to hear. Also, I guess this could > be > better documented. > > thanks, > sven
Ah, the thing is that the scripts are lying in a separate folder from the one I am using. I have a general repository for the scripts and "load" the functions within them whenever I need them (and improve them, too). Gretl itself seems to have no problem with scripts relative to the scripts own path if I have the script open. However, in my example, I have a script "A" for a current project open and from this load a script "B" which again loads a bunch of other scripts "C" defined with relative paths to "B". I do, however, not try to move "up" in the paths. Best Frederik
