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.
I don't fully get the problem, Frederik. For instance, a typical
structure I often use looks like
<hansl>
# Set some folder strings
string WD = "/home/at/Dropbox/DECRA_p2"
string est = "(a)WD/2.ESTIMATION"
string FUN = "/home/at/ownCloud/gretl_script" # additional functions
# Run setup script
run "(a)est/setup.inp"
</hansl>
within setup.inp I've got
<hansl>
# Load additional functions or pckg.
include "(a)est/g_Skript2_subroutines.inp"
</hansl>
I think this can handle everything one needs, doesn't it?
Artur