I am running with an absolute image path. The issue is definitely exec "$image" in the script. If I remove the "", i.e. exec $image, then it works. /opt/pharo/pharo6.1-64/bin/lib/pharo/5.0-201708271955/pharo "my.image startup.st" gives me the same problem On Wed, Jun 27, 2018 at 9:28 AM, Julián Maestri <serpi90@gmail.com> wrote:
Try with ./pharo or try with an absolute image path.
On Wed, Jun 27, 2018, 04:03 Tim Mackinnon <tim@testit.works> wrote:
Iâve not noticed that problem on ubuntu or AWS lambda so there must be something different going on.
Sent from my iPhone
On 27 Jun 2018, at 07:30, Otto Behrens <otto@finworks.biz> wrote:
Hi,
I just installed pharo 6.1 using the .zip file (http://files.pharo.org/ platform/Pharo6.1-64-linux.zip) and battled to start up pharo with arguments.
The issue is that the pharo bash script (in the extracted home dir) quotes all arguments:
# execute exec "$LINUX/pharo" \ --plugins "$LINUX" \ --encoding utf8 \ -vm-display-X11 \ "$image"
where
image = $*
The impact is that if I want to run a startup script, eg.
pharo my.image startup.st
pharo complains with "Could not open the Pharo image file: 'my.image startup.st'
So I must run the executable directly?
If so, some questions about the options that the bash script passes in: --plugins "$LINUX" is this necessary? will the default not be enough? --encoding utf8 the usage output says for example --textenc default is "UTF-8". Is utf8 the same thing? -vm-display-X11 I tried starting without this, and it worked. Do I need to explicitly start with this?
Thanks Otto