Am 04.01.2018 um 19:10 schrieb Schaff, Frederik:
> 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.
OK, I understand.
Perhaps you should either put your script repository where gretl will
always find it, like the user dir (see table 4.1 in the manual), which
under Windows should be
C:\Users\<yourusername>\Documents\gretl
and under Linux:
~/gretl
Then you wouldn't need to mess with paths at all in your scripts, just
do "include me.inp".
Or if for backup purposes or whatever you want to put them somewhere
else, switch to using "more absolute" paths. What I mean is paths that
are only relative to the user's home directory. (You can get that path
prefix on Windows with 'getenv("userprofile")', and on Linux with
'getenv("HOME")'.)
hth,
sven
