12:54 p.m.
Hi,
the following happened when running the awm.inp example file from the
SVAR addon on a console-only installation (Linux), within a "gretlcli"
session via gretl's 'run' command.
The awm.inp script must fail because it tries to send stuff to gnuplot
with the "display" option. That's understood. Here is some error output:
gnuplot stderr: '01:48:52 PM: Error: Unable to initialize GTK+, is
DISPLAY set properly?
Failed to initialize wxWidgets.
'
Failed command: 'gnuplot -persist "/home/gretlcheck/.gretl/gpttmp.plt"'
However, after that I don't get back to the gretlcli prompt ("?"), but
instead gretl(cli) terminates and I'm at the shell prompt. And I think
that's not right.
This is with current git.
thanks
sven
1:49 p.m.
On Fri, 22 Feb 2019, Sven Schreiber wrote:
Hi,
the following happened when running the awm.inp example file from the SVAR
addon on a console-only installation (Linux), within a "gretlcli" session via
gretl's 'run' command.
The awm.inp script must fail because it tries to send stuff to gnuplot with
the "display" option. That's understood. Here is some error output:
gnuplot stderr: '01:48:52 PM: Error: Unable to initialize GTK+, is DISPLAY
set properly?
Failed to initialize wxWidgets.
'
Failed command: 'gnuplot -persist
"/home/gretlcheck/.gretl/gpttmp.plt"'
However, after that I don't get back to the gretlcli prompt ("?"), but
instead gretl(cli) terminates and I'm at the shell prompt. And I think that's
not right.
This is with current git.
Uhm, that's strange, things work ok here.
It look as if you're running a remote ssh session without X tunneling.
-------------------------------------------------------
Riccardo (Jack) Lucchetti
Dipartimento di Scienze Economiche e Sociali (DiSES)
Università Politecnica delle Marche
(formerly known as Università di Ancona)
r.lucchetti(a)univpm.it
http://www2.econ.univpm.it/servizi/hpp/lucchetti
-------------------------------------------------------
2:03 p.m.
Am 22.02.2019 um 14:49 schrieb Riccardo (Jack) Lucchetti:
On Fri, 22 Feb 2019, Sven Schreiber wrote:
Uhm, that's strange, things work ok here.
Well, are you testing on a setup without desktop environment?
It look as if you're running a remote ssh session without X tunneling.
This is actually on the Linux Subsystem for Windows or what it's called
(WSL), in the form of a Debian userspace. But even if it were ssh
without X tunnel, shouldn't gretl recover gracefully from that error?
The error per se or my setup here is obviously not terribly important.
cheers
sven
6:52 p.m.
On Fri, 22 Feb 2019, Sven Schreiber wrote:
Hi,
the following happened when running the awm.inp example file from the SVAR
addon on a console-only installation (Linux), within a "gretlcli" session via
gretl's 'run' command.
The awm.inp script must fail because it tries to send stuff to gnuplot with
the "display" option. That's understood. Here is some error output:
gnuplot stderr: '01:48:52 PM: Error: Unable to initialize GTK+, is DISPLAY
set properly?
Failed to initialize wxWidgets.
'
Failed command: 'gnuplot -persist
"/home/gretlcheck/.gretl/gpttmp.plt"'
However, after that I don't get back to the gretlcli prompt ("?"), but
instead gretl(cli) terminates and I'm at the shell prompt. And I think that's
not right.
I've experimented with running a script containing deliberate errors
under "run" in gretlcli and mostly you get the interactive prompt
back. An error in calling gnuplot (or maybe an error in calling any
external program?) seems to be the exception. I'll see what I can find
out about this.
Allin
9:24 p.m.
On Fri, 22 Feb 2019, Allin Cottrell wrote:
On Fri, 22 Feb 2019, Sven Schreiber wrote:
> Hi,
>
> the following happened when running the awm.inp example file from the SVAR
> addon on a console-only installation (Linux), within a "gretlcli" session
> via gretl's 'run' command.
>
> The awm.inp script must fail because it tries to send stuff to gnuplot with
> the "display" option. That's understood. Here is some error output:
>
> gnuplot stderr: '01:48:52 PM: Error: Unable to initialize GTK+, is DISPLAY
> set properly?
> Failed to initialize wxWidgets.
> '
> Failed command: 'gnuplot -persist
"/home/gretlcheck/.gretl/gpttmp.plt"'
>
> However, after that I don't get back to the gretlcli prompt ("?"), but
> instead gretl(cli) terminates and I'm at the shell prompt. And I think
> that's not right.
I've experimented with running a script containing deliberate
errors under "run" in gretlcli and mostly you get the interactive
prompt back. An error in calling gnuplot (or maybe an error in
calling any external program?) seems to be the exception. I'll see
what I can find out about this.
Hmm, it's more complicated than I thought. In the Linux console (X
not running) I tried this script under "run" in gretlcli:
<hansl>
function scalar badplot (list L)
loop i=1..2 -q
gnuplot L --output=display
endloop
return 0
end function
function scalar topfunc (list L)
return badplot(L)
end function
open data4-10
list L = 1 2
x = topfunc(L)
</hansl>
You'll see that I'm trying to emulate the SVAR situation by putting
the (unrealizable) gnuplot call inside a loop, in a function called
by a function. Yet here, too, the inevitable failure of the plot
call lands me back at the gretlcli interactive prompt -- I'm not
dumped out to the shell.
So more investigation needed!
Allin
1:17 p.m.
Am 22.02.2019 um 22:24 schrieb Allin Cottrell:
Hmm, it's more complicated than I thought. In the Linux console
(X not
...
You'll see that I'm trying to emulate the SVAR situation by
putting the
(unrealizable) gnuplot call inside a loop, in a function called by a
function. Yet here, too, the inevitable failure of the plot call lands
me back at the gretlcli interactive prompt -- I'm not dumped out to the
shell.
So more investigation needed!
Well, so maybe this is specific to the Windows Subsystem for Linux after
all. Or were you able to replicate the failure with the awm.inp script?
thanks
sven
7:02 p.m.
On Sat, 23 Feb 2019, Sven Schreiber wrote:
Am 22.02.2019 um 22:24 schrieb Allin Cottrell:
> Hmm, it's more complicated than I thought. In the Linux console (X not
...
> You'll see that I'm trying to emulate the SVAR situation by putting the
> (unrealizable) gnuplot call inside a loop, in a function called by a
> function. Yet here, too, the inevitable failure of the plot call lands me
> back at the gretlcli interactive prompt -- I'm not dumped out to the shell.
>
> So more investigation needed!
Well, so maybe this is specific to the Windows Subsystem for Linux after all.
Or were you able to replicate the failure with the awm.inp script?
I should have said: yes, I can replicate the awm.inp failure in the
native Linux console. But I'm having difficulty determining what the
"active ingredient" is.
Allin
9:31 p.m.
On Sat, 23 Feb 2019, Allin Cottrell wrote:
On Sat, 23 Feb 2019, Sven Schreiber wrote:
> Am 22.02.2019 um 22:24 schrieb Allin Cottrell:
>
>> Hmm, it's more complicated than I thought. In the Linux console (X not
> ...
>
>> You'll see that I'm trying to emulate the SVAR situation by
>> putting the (unrealizable) gnuplot call inside a loop, in a
>> function called by a function. Yet here, too, the inevitable
>> failure of the plot call lands me back at the gretlcli
>> interactive prompt -- I'm not dumped out to the shell.
>>
>> So more investigation needed!
>
> Well, so maybe this is specific to the Windows Subsystem for
> Linux after all. Or were you able to replicate the failure with
> the awm.inp script?
I should have said: yes, I can replicate the awm.inp failure in
the native Linux console. But I'm having difficulty determining
what the "active ingredient" is.
Aha, finally found the source of the problem, which actually has
nothing to do with gnuplot or 3rd party programs in general.
Using "run" interactively in gretlcli has apparently been little
explored. The intent was that (a) a script executed in this mode
should be stopped at the first error (unless trapped by "catch") but
(b) even if the script errors out the user should be returned to the
gretlcli prompt (i.e. gretlcli itself should not be aborted, just as
the gretl GUI doesn't get aborted on an error in a script).
However there were two things wrong -- in "opposite directions", so
to speak:
1) If an error occurred within a loop at the top level of a script
called via "run", this caused gretlcli to exit. This was the case
with the SVAR example script awm.inp, when called in an environment
in which a plot could not be displayed.
2) Otherwise, even when "catch" was not deployed, an error in a
script called by "run" would not necessarily terminate the script's
execution.
Both of these points are now fixed in git; snapshots to follow.
Allin
2126
days inactive
2129
days old
7 comments
3 participants
participants (3)
-
Allin Cottrell -
Riccardo (Jack) Lucchetti -
Sven Schreiber