On Sun, 14 Jul 2019, Klára Major wrote:
Thank you! I checked and it does not solve the problem.
However I have been thinking and got some insights.
Thanks for investigating this!
C:\Users\MAJOR KLÁRA\AppData\Roaming\gretl\h.mat: No such file or
I just checked now: the command line version [of octave] can not
handle accented characters in the path.
So basically I think I know what the problem is and I can not
really solve it, unless it will become possible the specify the
folder exactly where gretl works (I mean mwrite, mread,
gretl_loadmat and gretl_export). Maybe in the future?
This could also be a problem with other third-party software on
Windows. Maybe we should let the user specify an "input_output_dir"
(that would presumably have a nice plain name!) as an alternative to
the default directory under "Users\<username>\AppData".
Or the other possible solution is if it is possible to write my
own gretl_export function for octave and bypass the default
version. This in itself would give me the flexibility to handle
these kind of difficulties.
You could indeed write a "my_gretl_export" function which targets a
different directory. On the gretl side, mread() can read from
anywhere you like if you specify the path. It looks under
AppData\Roaming only if you set the last argument to non-zero.