emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeremie Juste <jeremiejuste@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: source block evaluation in #+DATE line
Date: Tue, 10 May 2022 22:11:52 +0200	[thread overview]
Message-ID: <875ymdqh9z.fsf@gmail.com> (raw)
In-Reply-To: <87lev961yo.fsf@med.uni-goettingen.de> (Andreas Leha's message of "Tue, 10 May 2022 13:50:39 +0200")

Hello Andreas,

On Tuesday, 10 May 2022 at 13:50, Andreas Leha wrote:
> Hi all,
> how can I have a source block result in a #+Date line?
> I am creating a beamer presentation.  While the code works and the
> results get exported nicely at any other position, in the #+Date line
> only the code is exported.

> #+DATE:      Only Code Exported: src_sh[:exports results :results
> output wrap replace]{date}

I'm not sure I undersand, why you would want to use the shell to specify
a date. Could you please explain? Are you looking for a particular date

The example below, taken from the org documentation produces the current
date when exported to BEAMER.

#+TITLE: Example Presentation
#+AUTHOR: Carsten Dominik
#+OPTIONS: H:2 toc:t num:t
#+LATEX_CLASS: beamer
#+LATEX_CLASS_OPTIONS: [presentation]

* This is the first structural section

** Frame 1
*** Thanks to Eric Fraga                                           :B_block:
    :BEAMER_COL: 0.48
    :BEAMER_ENV: block
    for the first viable Beamer setup in Org
*** Thanks to everyone else                                        :B_block:
    :BEAMER_COL: 0.48
    :BEAMER_ACT: <2->
    :BEAMER_ENV: block
    for contributing to the discussion
**** This will be formatted as a beamer note                       :B_note:
     :BEAMER_env: note
** Frame 2 (where we will not use columns)
*** Request
    Please test this stuff!


  reply	other threads:[~2022-05-10 20:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 11:50 source block evaluation in #+DATE line Andreas Leha
2022-05-10 20:11 ` Jeremie Juste [this message]
2022-05-10 20:26   ` Kaushal Modi
2022-05-11  3:15     ` Andreas Leha
2022-05-11 16:50       ` Eric S Fraga
2022-05-11 17:07         ` Eric S Fraga
2022-05-12  7:53           ` Andreas Leha
2022-05-11 17:12 ` Timothy

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:

  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=875ymdqh9z.fsf@gmail.com \
    --to=jeremiejuste@gmail.com \
    --cc=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).