-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metta+>
Imperative Commands Not Working with swipl-win
#217
Comments
Can't reproduce exactly- repl starts but doesn't respond for me:
|
Also, this keeps happening when I start with mettalog_swipl-win_lines.mp4It happens intermittently without apparent reason (no changes to the command line, happens from a clean section, no changes in code etc). |
i can confirm it happens on my debian 12 linux
|
happens = doesnt have any reply output .. looks like you will need to run somethinjg like |
When running the MeTTa interpreter, I observe that imperative commands behave differently depending on whether I start with
swipl-win
orswipl
. Specifically, commands likeprolog.
(to drop into the Prolog shell) andls.
(to list directory contents) work when usingswipl
but do not function as expected when usingswipl-win
.Steps to Reproduce:
swipl -l prolog/metta_lang/metta_interp.pl
(console environment).swipl-win -l prolog/metta_lang/metta_interp.pl
(graphical environment).metta+>
prompt, try the following:prolog.
to enter the Prolog shell.ls.
to list directory contents.Expected Behavior:
Commands like
prolog.
andls.
should function the same way regardless of whetherswipl
orswipl-win
is used to start the MeTTa interpreter.Actual Behavior:
swipl
, these commands work as expected.swipl-win
, the commands fail to execute.Additional Information:
swipl
andswipl-win
is unclear.swipl-win
, it is not mentioned in the documentation.Request:
Please clarify whether
swipl-win
requires specific configuration to support these commands or if this is a limitation or bug. If it is a bug, a fix or workaround would be greatly appreciated.The text was updated successfully, but these errors were encountered: