From: Ista Zahn <istazahn@gmail.com>
To: Malcolm Purvis <malcolm@purvis.id.au>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Tangling and Exporting an Unsupported Language.
Date: Mon, 29 Sep 2014 15:22:13 -0400 [thread overview]
Message-ID: <CA+vqiLGt9TW-+NX=240gYrOhcHvcmCWgo2hw0XryYbveFXt7hQ@mail.gmail.com> (raw)
In-Reply-To: <m238badiij.fsf@purvis.id.au>
Exporting and tangling don't require any language support.
#+begin_src foobarbas :tangle foo.bar
#+end_src
is perfectly fine and will export and tangle just fine. Or did I
misunderstand your question?
Best,
Ista
On Mon, Sep 29, 2014 at 2:53 AM, Malcolm Purvis <malcolm@purvis.id.au> wrote:
> All,
>
> I'm writing an org document which contains code examples of a language
> not supported by Babel (a local domain specific language). The language
> doesn't even have a supporting Emacs mode.
>
> I'm wondering what the best portable approach is to managing the code
> blocks. I'm particularly interested in exporting the document to LaTeX
> and tangling the code. I may need to share the document with others, so
> I'd prefer not to require a supporting elisp file if I can help it.
>
> Currently I'm using the org language, since it seems to be the most generic:
>
> #+begin_src org :tangle foo.bar
> #+end_src
>
> Is there a case for 'begin_src text' to handle arbitrary content?
>
> Malcolm
>
> --
> Malcolm Purvis <malcolm@purvis.id.au>
>
next prev parent reply other threads:[~2014-09-29 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 6:53 Tangling and Exporting an Unsupported Language Malcolm Purvis
2014-09-29 19:22 ` Ista Zahn [this message]
2014-10-01 7:10 ` Malcolm Purvis
2014-10-01 14:22 ` Ista Zahn
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='CA+vqiLGt9TW-+NX=240gYrOhcHvcmCWgo2hw0XryYbveFXt7hQ@mail.gmail.com' \
--to=istazahn@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=malcolm@purvis.id.au \
/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).