From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Beamer :BEAMER_envargs: [allowframebreaks] not working
Date: Tue, 29 Sep 2015 05:12:00 +0100 [thread overview]
Message-ID: <olua8s5q2y7.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87612up8ep.fsf@gmail.com
Hi Jeremie,
Jeremie Juste <jeremiejuste@gmail.com> writes:
> Hello,
>
> It's my first post here finally. Most of my questions were answered
> before by you.:). I have the lastest version of org mode and search
> with the best of my abilities if any had the same issue but couldn't
> find anything.
>
> I have some difficulty with the org-mode variable :BEAMER_envargs.
>
> It does not allow frame break. There was a post on SO about the issue
>
> http://stackoverflow.com/questions/29384107/org-mode-framebreak-does-not-work-with-label-option-in-exported-beamer
>
> As a fix they recommend the following fix
> (setq org-beamer-frame-default-options "allowframebreaks,label=")
>
> This doesn't do the job and on the tex file it produces something like
> \begin{frame}[allowframebreaks,label=,label={sec:orgheadline1}]{part 1}
>
> I tried with
> (setq org-beamer-frame-default-options "allowframebreaks")
> but the results were not better,
>
>
> Finally removing label={sec:orgheadline1} did the job.
> \begin{frame}[allowframebreaks]{part 1}
>
> So I suspect there is a problem with label={sec:orgheadline1}.
>
>
> Can someone help please?
>
(Untested!)
I suspect that this is due to org-latex-prefer-user-labels being
nil. This will make Org mode inserting auto-generated labels.
Setting this to sth non-nil might work here.
HTH,
Andreas
next prev parent reply other threads:[~2015-09-29 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 20:59 Beamer :BEAMER_envargs: [allowframebreaks] not working Jeremie Juste
2015-09-29 4:12 ` Andreas Leha [this message]
2015-09-29 7:32 ` Eric S Fraga
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=olua8s5q2y7.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).