From: "Cook, Malcolm" <MEC@stowers.org>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: ox-html HOWTO? exporting #+RESULTS inside div
Date: Thu, 22 Oct 2015 06:13:56 +0000 [thread overview]
Message-ID: <1445494436616.55293@stowers.org> (raw)
In-Reply-To: <alpine.OSX.2.20.1510211904420.4099@charles-berrys-macbook.local>
Charles,
Excellent - that is precisely what I needed.
Additionally, I can avoid having to include the :wrap keyword on every header by specifying a single buffer-wide header arguments, such as
#+PROPERTY: header-args :wrap org-results-container
Thanks,
~ malcolm_cook@stowers.org
________________________________________
From: Charles C. Berry <ccberry@ucsd.edu>
Sent: Wednesday, October 21, 2015 9:18 PM
To: Cook, Malcolm
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-html HOWTO? exporting #+RESULTS inside div
On Wed, 21 Oct 2015, Cook, Malcolm wrote:
> Hi,
>
> I would like to contrive for the contents of results blocks to be
> embedded in a new div with a common class of org-results-container.
Try this:
--8<---------------cut here---------------start------------->8---
#+BEGIN_SRC shell :exports both :wrap org-results-container
echo "org results here"
#+END_SRC
--8<---------------cut here---------------end--------------->8---
which html export renders as
--8<---------------cut here---------------start------------->8---
<div class="org-results-container">
<p>
org results here
</p>
</div>
--8<---------------cut here---------------end--------------->8---
You can add a special-block filter if the <p> ... </p> is unwanted.
HTH,
Chuck
next prev parent reply other threads:[~2015-10-22 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 23:12 ox-html HOWTO? exporting #+RESULTS inside div Cook, Malcolm
2015-10-22 2:18 ` Charles C. Berry
2015-10-22 6:13 ` Cook, Malcolm [this message]
2015-11-05 0:02 ` Cook, Malcolm
2015-11-05 4:08 ` Charles C. Berry
2015-11-06 19:45 ` Cook, Malcolm
2015-11-06 21:01 ` Charles C. Berry
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=1445494436616.55293@stowers.org \
--to=mec@stowers.org \
--cc=ccberry@ucsd.edu \
--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).