1:24 p.m.
Is there a way to yield the dir-path of a script? I'd like to include scripts via a
"head"script, similar to c #include which is relative to the path.
i.e. In a script "c:/myscript.inp" I include a script
"c:/scriptfolder/script.inp" and this script in turn includes other scripts on
its own, relative to its path. E.g. with a line ' include "scripts/a.inp"
'. Currently this is not working and I guess the reason is that gretl looks for
"scripts/a.inp" relative to the scriptdir in which I included
"c:/scriptfolder/script.inp"; i.e. it tries to open "c:/scripts/a.inp"
and not "c:/scriptfolder/scripts/a.inp" (in this example)
Best
Frederik
1:52 p.m.
Hi Frederik,
have tried using "run SCRIPT.inp" instead of "include"?
Hi Artur,
that's interesting. Didn't know that command. Actually, it works and after it was
used only once in my "head" file, the subsequent includes work fine. I guess
"run" changes the gretl workingdir or so. However, it also prints all the file
content ... is there an option to make it "silent"?
Best
Frederik
1:59 p.m.
Hi Artur,
that's interesting. Didn't know that command. Actually, it works and after it was
used only once in my "head" file, the subsequent includes work fine. I guess
"run" changes the gretl workingdir or so. However, it also prints all the file
content ... is there an option to make it "silent"?
Glad it works. No, there is no silent option. Just put "set verbose off"
at the beginning of each script which is called.
Best,
Artur
3:11 p.m.
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.
-----Ursprüngliche Nachricht-----
Von: gretl-users-bounces(a)lists.wfu.edu [mailto:gretl-users-
bounces(a)lists.wfu.edu] Im Auftrag von Artur Tarassow
Gesendet: Donnerstag, 4. Januar 2018 15:00
An: gretl-users(a)lists.wfu.edu
Betreff: Re: [Gretl-users] dotdir / getenv alternative for scriptdir?
> Hi Artur,
>
> that's interesting. Didn't know that command. Actually, it works and after
it
was used only once in my "head" file, the subsequent includes work fine. I
guess "run" changes the gretl workingdir or so. However, it also prints all
the
file content ... is there an option to make it "silent"?
Glad it works. No, there is no silent option. Just put "set verbose off"
at the beginning of each script which is called.
Best,
Artur
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users
3:49 p.m.
Am 04.01.2018 um 16:11 schrieb Schaff, Frederik:
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
6:10 p.m.
> 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
6:15 p.m.
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
7:01 p.m.
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
9:07 p.m.
Dear Sven and Artur,
many thanks. I tried Arturs approach (as I understood it), but to no avail. If I got you
correct, Artur, you pass the information of the path "by memory". I.e. before
loading the first script, you save a string with that scripts path and then, in that
script, you make use of this path. For me that did not work...
I will instead make use of Svens suggestion and checkout the working copy into one of the
gretl folders, directly.
Thx!
Frederik
-----Ursprüngliche Nachricht-----
Von: gretl-users-bounces(a)lists.wfu.edu [mailto:gretl-users-
bounces(a)lists.wfu.edu] Im Auftrag von Sven Schreiber
Gesendet: Donnerstag, 4. Januar 2018 20:02
An: gretl-users(a)lists.wfu.edu
Betreff: Re: [Gretl-users] dotdir / getenv alternative for scriptdir?
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
_______________________________________________
Gretl-users mailing list
Gretl-users(a)lists.wfu.edu
http://lists.wfu.edu/mailman/listinfo/gretl-users
2530
days inactive
2530
days old
9 comments
3 participants
participants (3)
-
Artur Tarassow -
Schaff, Frederik -
Sven Schreiber