Has anyone gotten ediprolog to work with the docker image?

[bmaddy]

I'm trying to get ediprolog.el working with the docker image of scryer prolog. I've been able to get ediprolog working with the apt installed swi-prolog and the snap for swi-prolog, but when I try with the docker version of scryer-prolog, I get errors.

Here are some of the things I've tried. For each setup, I've been trying to run ediprolog-dwim on this line:

?- use_module(library(lists)).

The comments after each setup are what I see in ediprolog-history.

  (setq ediprolog-system 'swi)
  (setq ediprolog-program "/usr/bin/swipl")
  ;; works

  (setq ediprolog-system 'swi)
  (setq ediprolog-program "/snap/bin/swi-prolog.swipl")
  ;; works

  (setq ediprolog-program "docker run -v .:/mnt -v /tmp:/tmp -it mjt128/scryer-prolog")
  ;; Dec  5 00:04:42: starting: ("docker run -v .:/mnt -v /tmp:/tmp -it mjt128/scryer-prolog")
  ;; No prompt found.


  (setq ediprolog-program "docker")
  (setq ediprolog-program-switches '("run" "-v" ".:/mnt" "-v" "/tmp:/tmp" "-it" "mjt128/scryer-prolog"))
  ;; Dec  5 00:06:41: starting: ("docker" "run" "-v" ".:/mnt" "-v" "/tmp:/tmp" "-it" "mjt128/scryer-prolog")
  ;; �[?2004h�[6n
  ;; �[K?- 
  ;; �[3C
  ;; No prompt found.

I've also tried using a wrapper shell script that works fine when called on the command line, but not when ediprolog starts it. Additionally, I've tried using the elisp debugger to track down the problem, but haven't been able to find it (probably because I am not vary familiar with it).

Has anyone else tried this and gotten it working?

[bmaddy]

This is probably obvious to seasoned emacs users, but the output from that last example actually looks like this in the buffer (the above was a copy/paste):

^[[?2004h^[[6n^M^[[K?- ^M^[[3C

I may have made a little progress on this. Here's a snippet from the ediprolog-wait-for-prompt-filter function:

    (when (re-search-backward
           (format "^%s" (regexp-quote (ediprolog-prompt))) nil t)
      (with-current-buffer (process-buffer proc)
        (setq ediprolog-seen-prompt t)))))

It expects the prompt to be at the start of the line, but that's not the case because of the ANSI escape codes. I'm still not sure where the problem is though. I'll keep looking.

[triska]

The presence of ANSI escape codes seems to indicate that Scryer does not detect that it is being used in an environment that cannot interpret them.

You can try setting the environment variable TERM to the value dumb before launching Scryer Prolog. This is the value I get when I use ediprolog.el within Emacs. For instance, here is a portion of the *ediprolog-history* buffer after querying the environment variable with getenv/2 within Emacs:

Dec  5 18:57:34: starting: ("~/scryer-prolog/target/release/scryer-prolog")
?- use_module(library(os)).
   true.
?- getenv("TERM", X).
   X = "dumb".

[bmaddy]

That worked! Thank you so much!!

For anyone following along, here's the config that worked for me:

  (setq ediprolog-program "docker")
  (setq ediprolog-program-switches '("run" "-v" ".:/mnt" "-v" "/tmp:/tmp" "-e" "TERM=dumb" "-it" "mjt128/scryer-prolog"))

The *ediprolog-history* I get has some ^M newlines still, but that's something I can live with for now.

Dec  5 14:26:25: starting: ("docker" "run" "-v" ".:/mnt" "-v" "/tmp:/tmp" "-e" "TERM=dumb" "-it" "mjt128/scryer-prolog")
?- use_module(library(lists)).
use_module(library(lists)).^M
   true.^M
?- member(X, [a,b,c]).
member(X, [a,b,c]).^M
   X = a;^M
;  X = b;^M
;  X = c.^M
?- 

[triska]

Great, I am glad it is working acceptably for now! The interaction looks unusual though: Why are the queries repeated in the history buffer? Could you please post a screenshot of the *ediprolog-history* buffer in this state? The colors will indicate what was sent to the process, and what was received.

[bmaddy]

[triska]

Thank you! That's indeed not how it is supposed to work: From the screenshot, we see that member(X, [a,b,c]) was sent to the Scryer process, and then the process responds by sending the same string it received.

For comparison, I get: