From: Michael Gauland <mikelygee@no8wireless.co.nz>
To: emacs-orgmode@gnu.org
Subject: [new exporter] :wrap problems
Date: Wed, 5 Dec 2012 20:31:37 +0000 (UTC) [thread overview]
Message-ID: <loom.20121205T212010-146@post.gmane.org> (raw)
I've run into trouble using the :wrap option with babel, with the new exporter.
Using :wrap to put the result in an EXAMPLE block works consistently, but
putting the result into a SRC block is inconsistent. This example:
* :wrap example
#+BEGIN_SRC ruby :results value :exports both :wrap EXAMPLE
"This string came from Ruby."
#+END_SRC
#+BEGIN_SRC ruby :results value :exports both :wrap SRC fundamental
"This string also came from Ruby."
#+END_SRC
Works as I would expect with the old exporter, but the new exporter does not
process the generated SRC block. Exporting to ASCII gives me:
:wrap example
=============
,----
| "This string came from Ruby."
`----
,----
| This string came from Ruby.
`----
,----
| "This string also came from Ruby."
`----
#+BEGIN_SRC fundamental This string also came from Ruby.
#+END_SRC fundamental
The HTML and LaTeX exporters behave similarly (ie., the old exporters work; the
new ones don't). The org files I'm using contain several such blocks, and I've
found that some will be exported corretly, and others won't, though I haven't
noticed any pattern.
Can anyone verify that this behaviour is not unique to my system (and perhaps
suggest where the problem may be?)
Kind Regards,
Mike Gauland
next reply other threads:[~2012-12-05 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 20:31 Michael Gauland [this message]
2012-12-05 20:42 ` [new exporter] :wrap problems Nicolas Goaziou
2012-12-05 21:25 ` Michael Gauland
2012-12-05 21:27 ` [PATCH] Babel: Fix the #+END_ directive from the :wrap param Michael Gauland
2012-12-19 20:17 ` Nicolas Goaziou
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=loom.20121205T212010-146@post.gmane.org \
--to=mikelygee@no8wireless.co.nz \
--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).