From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: BUG: in beamer export non-beamer tags exported as part of header
Date: Wed, 25 May 2016 22:29:51 +0200 [thread overview]
Message-ID: <87mvndc24g.fsf@saiph.selenimh> (raw)
In-Reply-To: <m2bn3uvbap.fsf@krugs.de> (Rainer M. Krug's message of "Wed, 25 May 2016 09:37:01 +0200")
Hello,
Rainer M Krug <Rainer@krugs.de> writes:
> Makes sense - I just wasn't aware of the tags:nil property. Probably it
> should be added to the beamer template headers (C-ce#)?
It belongs to the default template, since this is a generic option.
I don't think it's a good idea to add duplicates in templates.
> I had
>
> #+OPTIONS: tags:not-in-toc
>
> in my org file, but the tags were still in the toc of the beamer
> export.
From your document, adding tags:not-in-toc, I get
\begin{document}
\begin{frame}{Outline}
\tableofcontents
\end{frame}
\section[Level 1]{Level 1\hfill{}\textsc{presentation}}
\label{sec:org057dfd7}
\begin{frame}[label={sec:org1551704}]{Frame 1}
Some Text
\end{frame}
\end{document}
Do you know what should be generated instead?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-05-25 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 10:48 BUG: in beamer export non-beamer tags exported as part of header Rainer M Krug
2016-05-24 12:08 ` Rasmus
2016-05-24 12:27 ` Rainer M Krug
2016-05-24 20:32 ` Nicolas Goaziou
2016-05-24 21:02 ` Rasmus
2016-05-25 7:39 ` Rainer M Krug
2016-05-25 7:37 ` Rainer M Krug
2016-05-25 20:29 ` Nicolas Goaziou [this message]
2016-05-27 9:01 ` Rainer M Krug
2016-05-27 11:58 ` Nicolas Goaziou
2016-05-27 16:15 ` Rainer M Krug
2016-05-31 19:53 ` Nicolas Goaziou
2016-06-01 8:06 ` Rainer M Krug
2016-06-01 11:08 ` Nicolas Goaziou
2016-06-01 12:21 ` Rasmus
2016-06-01 13:23 ` Rainer M Krug
2016-06-01 17:40 ` Nicolas Goaziou
2016-05-31 20:07 ` John Hendy
2016-06-01 8:12 ` Rainer M Krug
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=87mvndc24g.fsf@saiph.selenimh \
--to=mail@nicolasgoaziou.fr \
--cc=Rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).