From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: emacs-orgmode@gnu.org
Subject: Re: Placement of \makeatletter with \beamer@frametextheight
Date: Fri, 30 Nov 2018 08:13:11 +0100 [thread overview]
Message-ID: <87h8fzvy0o.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: 0551ef45-6401-340f-d6ab-a6fc5549e29e@eureca.de
Julius Müller <Julius.S.Mueller@eureca.de> writes:
> Am 29.11.18 um 14:07 schrieb Loris Bennett:
[snip (33 lines)]
>> After that I tried adding the definition on the slide itself
>>
>> #+BEGIN_SRC latex
>> \newlength\mytextheight\makeatletter\setlength\mytextheight{\beamer@frametextheight}\makeatother
>> #+END_SRC
>
> Hm, src-block? I would have thought you should wrap that in an
> export-block, so those commands get added to the exported document, not
> quoted within as a source code. That would mean
>
> #+begin_export latex
> \newlength\mytextheight\makeatletter\setlength\mytextheight{\beamer@frametextheight}\makeatother
> #+end_export
I tried that, but still got the error about \beamer being undefined.
However, my understanding is that, if I am exporting to LaTeX, then
BEGIN_SRC latex
and
BEGIN_EXPORT latex
do the same thing. So if I have the following in my org file:
#+BEGIN_EXPORT latex
\newlength\mytextheight\makeatletter\setlength\mytextheight{\beamer@frametextheight}\makeatother
#+END_EXPORT
#+BEGIN_SRC latex
\newlength\mytextheight\makeatletter\setlength\mytextheight{\beamer@frametextheight}\makeatother
#+END_SRC
I get
\newlength\mytextheight\makeatletter\setlength\mytextheight{\beamer@frametextheight}\makeatother
\newlength\mytextheight\makeatletter\setlength\mytextheight{\beamer@frametextheight}\makeatother
in my tex file.
Cheers,
Loris
--
This signature is currently under construction.
prev parent reply other threads:[~2018-11-30 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 15:09 Placement of \makeatletter with \beamer@frametextheight Loris Bennett
2018-11-28 15:37 ` Eric S Fraga
2018-11-29 7:17 ` Loris Bennett
2018-11-29 8:13 ` Julius Dittmar
2018-11-29 8:38 ` Julius Dittmar
2018-11-29 9:26 ` Eric S Fraga
2018-11-29 13:07 ` Loris Bennett
2018-11-29 13:24 ` Gustavo Barros
2018-11-29 13:41 ` Joost Kremers
2018-11-29 15:12 ` Loris Bennett
2018-11-29 17:50 ` Eric S Fraga
2018-11-29 13:47 ` Julius Müller
2018-11-30 7:13 ` Loris Bennett [this message]
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=87h8fzvy0o.fsf@hornfels.zedat.fu-berlin.de \
--to=loris.bennett@fu-berlin.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).