From: "Thomas S. Dye" <tsd@tsdye.com>
To: Lawrence Bottorff <borgauf@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Babel prolog not working
Date: Wed, 25 Jan 2017 16:38:48 -1000 [thread overview]
Message-ID: <m2efzqzgsn.fsf@dhcp-168-105-17-8.wireless.manoa.hawaii.edu> (raw)
In-Reply-To: <CAFAhFSXjig22dNfsbgRR47B0qNRJm62puZqA6iivEMzCND11Bw@mail.gmail.com>
Aloha Lawrence,
Lawrence Bottorff writes:
> On my original system, as well on a built-from-scratch system, babel prolog
> won't work for me. I've got latest swi-prolog 7.4.0 installed, along with
> Emacs 25.1.1, and org 9.0.4, along with ob-prolog 20170102.953, and prolog
> (major mode) 1.22. Anything I put in a code block, e.g.,
>
> #+BEGIN_SRC prolog
> [likes.pl].
> #+END_SRC
>
> results in (*Messages*)
>
> executing Prolog code block...
> executing Prolog source code block
> org-babel-variable-assignments:prolog: Wrong number of arguments: (1 . 1), 2
>
> Doing C-h f brings up
>
> org-babel-variable-assignments:prolog is a compiled Lisp function in
> ‘ob-prolog.el’.
> (org-babel-variable-assignments:prolog PARAMS)
> Not documented.
>
> . . . and I found it in
> https://github.com/ljos/ob-prolog/blob/master/ob-prolog.el, but can't
> fathom what is going wrong.
>
> Regular, non-org prolog major mode interactions work fine.
>
> I know I try everyone's patience on this list, but I'm trying out many
> different languages' babel capabilities -- and reporting my "findings."
Perhaps you could also open an issue with the ob-prolog developer:
https://github.com/ljos/ob-prolog
One way to report "findings" is the Babel languages page on Worg:
http://orgmode.org/worg/org-contrib/babel/languages.html
That page could always use more love.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2017-01-26 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 2:08 Babel prolog not working Lawrence Bottorff
2017-01-26 2:38 ` Thomas S. Dye [this message]
2017-01-26 3:39 ` Lawrence Bottorff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2efzqzgsn.fsf@dhcp-168-105-17-8.wireless.manoa.hawaii.edu \
--to=tsd@tsdye.com \
--cc=borgauf@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).