emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Diego Zamboni <diego@zzamboni.org>
To: "Berry, Charles" <ccberry@health.ucsd.edu>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: How to wrap Org code generated by a source block?
Date: Tue, 10 Nov 2020 19:10:13 +0100	[thread overview]
Message-ID: <CAGY83EcuDQfcPu_dwwMLp4Rog+oDhV4USt8vwa6E8gzz89q8hw@mail.gmail.com> (raw)
In-Reply-To: <43B88A5C-E21D-42B5-9AC7-F33908FB4EEC@health.ucsd.edu>

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

Hi Chuck,

Thanks! =:results drawer= is exactly what I was looking for :)

I tried also with =:wrap src org=, but then upon export it's exported
literally as Org src code, instead of interpreted as such. The drawer was
exactly what I needed, and allows reevaluation of the block, replacing all
the results correctly.

Cheers,
--Diego


On Tue, Nov 10, 2020 at 6:41 PM Berry, Charles <ccberry@health.ucsd.edu>
wrote:

>
>
> > On Nov 10, 2020, at 6:13 AM, Diego Zamboni <diego@zzamboni.org> wrote:
> >
> > I want to generate some parts of my document programmatically from an
> emacs-lisp src block - i.e. the code produces Org markup which I want to
> then export. Is there a way to wrap the #+RESULTS block in an environment
> that still gets evaluated as Org text (e.g. when exporting)?
> >
> >
>
>
> Try `:results drawer'
>
> You can also do fancy stuff using `:wrap "src ..."' where `...' is a
> language and additional header args. One language choice is `org', but I
> don't think this approach is what you need.
>
> HTH,
> Chuck
>

[-- Attachment #2: Type: text/html, Size: 1569 bytes --]

  reply	other threads:[~2020-11-10 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 14:13 Diego Zamboni
2020-11-10 17:41 ` Berry, Charles via General discussions about Org-mode.
2020-11-10 18:10   ` Diego Zamboni [this message]
2020-11-10 20:13     ` Berry, Charles via General discussions about Org-mode.
2020-11-11  1:44     ` Ihor Radchenko

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=CAGY83EcuDQfcPu_dwwMLp4Rog+oDhV4USt8vwa6E8gzz89q8hw@mail.gmail.com \
    --to=diego@zzamboni.org \
    --cc=ccberry@health.ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: How to wrap Org code generated by a source block?' \
    /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

Code repositories for project(s) associated with this 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).