8:09 p.m.
If I want to execute the commandline gretl on OS X will this suffice (in a terminal of
course)?
/Applications/Gretl.app/Contents/Resources/bin/gretlcli <any options>
Berend
1:57 a.m.
On Fri, 21 Nov 2014, Berend Hasselman wrote:
If I want to execute the commandline gretl on OS X will this
suffice (in a terminal of course)?
/Applications/Gretl.app/Contents/Resources/bin/gretlcli <any options>
Good question, and sorry I haven't got to it sooner.
The answer is basically yes, but there are some finer points that
need attention if we're serious about supporting gretlcli on the
Mac.
Yes: the invocation above should start gretlcli OK, and most things
should work, provided the GUI program has been run beforehand and
therefore a valid ~/.gretl2rc file has been created in the user's
home directory.
Finer points: one of these is that invoking gnuplot via gretlcli is
unlikely to work. That's because the gnuplot executable that's
supplied in the gretl package will probably not be in the user's
PATH. (It should work OK with the GUI, because the GUI program is
launched via a script that sets up all the requisite environment
variable magic.)
Maybe we should move the real gretlcli binary to, say, gretlcli.bin
and install a script named gretlcli which calls gretlcli.bin with
the relevant environment variables set appropriately. We haven't
paid much attention to this so far, on the assumption that 99 point
something percent of Mac users will never have any occasion to use
the CLI program. But we should also consider the "one percent"!
(And I guess we could say the same goes for Windows -- although in
that case the CLI is even less likely to be used since there is by
default no half-way usable shell on Windows, while the Mac has a
pretty decent terminal program that runs bash, even if nobody but
l33t haxors knows about it.)
Allin Cottrell
7:57 a.m.
On Wed, 26 Nov 2014, Allin Cottrell wrote:
Maybe we should move the real gretlcli binary to, say, gretlcli.bin
and install a script named gretlcli which calls gretlcli.bin with
the relevant environment variables set appropriately. We haven't
paid much attention to this so far, on the assumption that 99 point
something percent of Mac users will never have any occasion to use
the CLI program. But we should also consider the "one percent"!
Not to mention the fact that, for running heavy-duty tasks, using the cli
interface is largely preferable for a number of reasons. It even gives you
a modest performance gain compared to the GUI interface.
(And I guess we could say the same goes for Windows -- although in
that case the CLI is even less likely to be used since there is by
default no half-way usable shell on Windows, while the Mac has a
pretty decent terminal program that runs bash, even if nobody but
l33t haxors knows about it.)
I know very little about it, but I believe that recent versions of windows
have something called the "power shell", or something like that, which is
a much more serious alternative to bash. It's even got a scripting
language which, I am told, is quite powerful and flexible. That said, I
suspect that the share of windows users which are even aware of it is far,
far from 1%.
-------------------------------------------------------
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
-------------------------------------------------------
6:19 p.m.
Allin Cottrell wrote:
On Fri, 21 Nov 2014, Berend Hasselman wrote:
> If I want to execute the commandline gretl on OS X will this
> suffice (in a terminal of course)?
>
> /Applications/Gretl.app/Contents/Resources/bin/gretlcli<any options>
Good question, and sorry I haven't got to it sooner.
The answer is basically yes, but there are some finer points that
need attention if we're serious about supporting gretlcli on the
Mac.
I hadn't realised that.
Yes: the invocation above should start gretlcli OK, and most things
should work, provided the GUI program has been run beforehand and
therefore a valid ~/.gretl2rc file has been created in the user's
home directory.
Finer points: one of these is that invoking gnuplot via gretlcli is
unlikely to work. That's because the gnuplot executable that's
supplied in the gretl package will probably not be in the user's
PATH. (It should work OK with the GUI, because the GUI program is
launched via a script that sets up all the requisite environment
variable magic.)
Maybe we should move the real gretlcli binary to, say, gretlcli.bin
and install a script named gretlcli which calls gretlcli.bin with
the relevant environment variables set appropriately. We haven't
paid much attention to this so far, on the assumption that 99 point
something percent of Mac users will never have any occasion to use
the CLI program. But we should also consider the "one percent"!
Good idea. Another suggestion: do something similar for the gnuplot
contained in Gretl. I could get rid of my self compiled gnuplot with
external AquaTerm support. I would only need two symlinks to be able to
use gretlcli and gnuplot when that is needed or advantageous.
Berend
3690
days inactive
3696
days old
3 comments
3 participants
participants (3)
-
Allin Cottrell -
Berend Hasselman -
Riccardo (Jack) Lucchetti