From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-mode for swi-prolog and latex export ?
Date: Mon, 21 Jul 2014 06:19:35 -0400 [thread overview]
Message-ID: <8761ir3tfs.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 87fvhvni8c.fsf@gmail.com
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> writes:
>
>> 2014-07-21 6:16 GMT+02:00 Nick Dokos <ndokos@gmail.com>:
>>
>> The first sentence of the doc that Tom pointed to is:
>>
>> ,----
>> | The core Babel functions (viewing, export, tangling, etc…) are
>> language
>> | agnostic and will work even for languages that are not
>> explicitly
>> | supported. Explicit language-specific support is required only
>> for
>> | evaluation of code blocks in a language.
>> `----
>>
>> So maybe nothing more is needed for just exporting and tangling
>> (completely untested).
>>
>> Yes, but I do not know how to define such and such language to export.
>> When I Cc -Ce I can export to latex and html for example , but I do
>> not know how to extend this list.
>
I don't understand: what language are you trying to export to? My take
was that you export the doc to latex/pdf/html and you tangle the code
fragments to some arbitrary file (a file that can be fed to a prolog
interpeter to be executed).
> This is a (lisp)programmers task. The usual proceeding would be to look
> at the list of extisting ob-<language>.el files and pick a language that
> is very similar to the new one (in case of prolog maybe a difficult
> task?). Then try to adapt this file to your new language -> ob-prolog.el.
Assuming that the statement I quoted is true, one should be able to
export files that contain prolog code fragments:
#+BEGIN_SRC prolog
foo
#+END_SRC
One has to do `:exports code' since exporting results would require
evaluation which *would* require that one write an ob-prolog.el.
Also, one should be able to tangle the prolog code fragment(s) into
files (no ob-prolog.el needed).
Exporting and tangling are generic services that babel provides even if
there is no evaluation for that language.
But as I said, I have not tried it: I am only trying to interpret what
the doc is saying, so when the eating comes, the pudding may be stale.
If the interpretation is wrong, I would love to be corrected. If the
interpretation is right, but the exporting/tangling does not work, then
that would be a babel bug.
Nick
next prev parent reply other threads:[~2014-07-21 10:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 7:54 org-mode for swi-prolog and latex export ? Joseph Vidal-Rosset
2014-07-20 8:05 ` Thorsten Jolitz
2014-07-20 20:37 ` Joseph Vidal-Rosset
2014-07-20 21:38 ` Thomas S. Dye
2014-07-21 4:16 ` Nick Dokos
2014-07-21 9:15 ` Joseph Vidal-Rosset
2014-07-21 10:01 ` Thorsten Jolitz
2014-07-21 10:19 ` Nick Dokos [this message]
2014-07-21 10:34 ` Joseph Vidal-Rosset
2014-07-21 13:40 ` Nick Dokos
2014-07-21 17:49 ` Joseph Vidal-Rosset
2014-07-21 18:27 ` Nick Dokos
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=8761ir3tfs.fsf@alphaville.bos.redhat.com \
--to=ndokos@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).