You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I downloaded the latest nightly version today, and I noticed the batch file does nothing when I tried to run it. I checked what changed with the file or the structure since then, and supposedly nothing. After lot of fruitless debugging, I tried moving the extracted folder to a different folder, and it just worked. Granted, the folder it was in had Unicode symbols, but I tried the older versions in the same folder, and they worked there without a hitch.
After more debugging, I don't think the issue is something with the %~dp0 or the start command, the outputs look fine, and it was able to launch a different executable placed in the Pharo/ folder successfully. The ERRORLEVEL variable is set to 0 after trying to launch Pharo, but I think it likely just fails without setting it properly.
To be clear, I do not believe this is an issue with OpenPonk (as in an issue that could be fixed here alone), but I wanted it to be documented in some way, since someone else might encounter it too.
The text was updated successfully, but these errors were encountered:
That's weird, I do not have any info from others about these not working. I see you created the issue regarding unicode chars - so the script works in ASCII-only paths?
It appears so, yes. But again, to be clear, the script as such behaves correctly (it didn't change since the P10 version, which worked just fine), it's the Pharo VM that is suddenly crashing when the image path contains Unicode characters.
I downloaded the latest nightly version today, and I noticed the batch file does nothing when I tried to run it. I checked what changed with the file or the structure since then, and supposedly nothing. After lot of fruitless debugging, I tried moving the extracted folder to a different folder, and it just worked. Granted, the folder it was in had Unicode symbols, but I tried the older versions in the same folder, and they worked there without a hitch.
After more debugging, I don't think the issue is something with the
%~dp0
or thestart
command, the outputs look fine, and it was able to launch a different executable placed in thePharo/
folder successfully. TheERRORLEVEL
variable is set to 0 after trying to launch Pharo, but I think it likely just fails without setting it properly.To be clear, I do not believe this is an issue with OpenPonk (as in an issue that could be fixed here alone), but I wanted it to be documented in some way, since someone else might encounter it too.
The text was updated successfully, but these errors were encountered: