Can't make it work. . .

[borgauf]

This may sound vague, but I'm on Emacs 26.3 and have latest org-mode, latest stable SWI-Prolog, but nothing I do seems to make Prolog in org-mode work. Can you perhaps give us a more detailed setup and execution tutorial?

[ljos]

It might be that there is something new with the latest versions. There is a second issue that hints that something changed. I will have a look when I have the time.

[borgauf]

I tried it with latest-greatest everything bare-bones emacs -Q as well as with my regular .emacs.d setup, both producing the same problems, i.e., no real babel interaction. Thanks for your efforts so far. . . .

…

On Mon, Nov 4, 2019 at 2:13 AM Bjarte Johansen ***@***.***> wrote: It might be that there is something new with the latest versions. There is a second issue that hints that something changed. I will have a look when I have the time. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21?email_source=notifications&email_token=ABA73W7PXSG45RRL5XACIUDQR7KRVA5CNFSM4JIPKGW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC6POKI#issuecomment-549254953>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABA73W26GLK7HD5Q544NI33QR7KRVANCNFSM4JIPKGWQ> .

[ljos]

If you look in the README now there are some instruction that you can follow. Let me know if you get it working (or not).

[ljos]

Basically, you need to add ob-prolog.el to the load path and as a language that org-babel can use.

There is still #20 that I couldn't figure out. So sessions won't work. Either it is a emacs bug or some strange interaction with some of the hooks that I have to add.

[borgauf]

I could list out everything about my setup. Or you could simply give me an exact emacs -Q setup that works on your end. Give me your system details, prolog version etc. too.

…

On Wed, Nov 6, 2019 at 2:40 AM Bjarte Johansen ***@***.***> wrote: Basically, you need to add ob-prolog.el to the load path and as a language that org-babel can use. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21?email_source=notifications&email_token=ABA73W7ADJ7HNM3OU4Q7YP3QSJ7JDA5CNFSM4JIPKGW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDFXO3Y#issuecomment-550205295>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABA73W2CFDEQEMYVASCEWDTQSJ7JDANCNFSM4JIPKGWQ> .

[ljos]

• Org mode version 9.1.9
• GNU Emacs 26.3
• SWI-Prolog version 8.0.3

emacs -q -l ob-prolog.el --eval "(org-babel-do-load-languages 'org-babel-load-languages '((prolog . t)))" test/test-ob-prolog.org

If I run the first test in that file I get the result:

| Hello | org_mode.  |

[borgauf]

Sorry for the late reply, but I'm still experiencing weird behavior. Yes, that first test snaps back #+RESULTS: basic-test | Hello | org_mode. | in the org buffer, as does the second test. However, the third test * Simple running session #+NAME: session-test #+HEADER: :session *prolog-1* #+HEADER: :goal fourtyone(A) #+BEGIN_SRC prolog fourtyone(A) :- A is 41. #+END_SRC seems to hang -- the same behavior I had mentioned before. But a C-g suddenly "releases" it and in the *prolog-1* buffer suddenly appears 1 ?- consult(user). |: |: fourtyone(A) :- A is 41. |: true. Likewise the rest of them, i.e., no org buffer RESULTS block, rather, a C-g, then the reply appearing in the *prolog-1* buffer: 2 ?- consult(user). |: |: answer(C) :- |: fourtyone(B), |: C is B+1. |: true. 2 ?- consult(user). |: |: :- recorda('a', [1, 2, 3]). |: :- recorda('b', 0). |: main(B) :- recorded(a, A), recorded(b, C), append([C], A, B). |: true. 2 ?- I don't think this is the intended behavior -- or is it? Thanks, LB

…

On Fri, Nov 8, 2019 at 4:11 AM Bjarte Johansen ***@***.***> wrote: - Org mode version 9.1.9 - GNU Emacs 26.3 - SWI-Prolog version 8.0.3 emacs -q -l ob-prolog.el --eval "(org-babel-do-load-languages 'org-babel-load-languages '((prolog . t)))" test/test-ob-prolog.org If I run the first test in that file I get the result: | Hello | org_mode. | — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21?email_source=notifications&email_token=ABA73W3JRSO2B3JVKHCX7FDQSU3MJA5CNFSM4JIPKGW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDPWISI#issuecomment-551511113>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABA73W6VGDQFXICJRSJ3WJTQSU3MJANCNFSM4JIPKGWQ> .

[ljos]

It is not intended, but it is a known issue (see #20). :session doesn't work right now. I think it is some mismatch in how consult(user) is handled. It is difficult to debug as there are callbacks etc. I will try and have a look again tonight if I get the time.

Closing the main issue here as fixed and deferring the remaining problem to #20.