From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Loris Bennett <loris.bennett@fu-berlin.de>, emacs-orgmode@gnu.org
Subject: Re: Placement of \makeatletter with \beamer@frametextheight
Date: Thu, 29 Nov 2018 11:24:15 -0200 [thread overview]
Message-ID: <9904e5c3-cfec-458e-426b-2f69b586d570@gmail.com> (raw)
In-Reply-To: <87lg5cowv7.fsf@hornfels.zedat.fu-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 1925 bytes --]
Louis,
a hunch, which might work.
It seems that, if you try to set the length in your preamble,
`\beamer@frametextheight` is not yet defined.
So, you might try the hook `\AtBeginDocument` to see if the definition
comes at a better timing.
#+LATEX_HEADER:
\newlength\mytextheight\AtBeginDocument{\makeatletter\setlength\mytextheight{\beamer@frametextheight}\makeatother}
As I said, it's a hunch, for I haven't tested. But I think it may be it.
Best,
Gustavo.
On 29/11/2018 11:07, Loris Bennett wrote:
> Eric S Fraga <esflists@gmail.com> writes:
>
>> On Thursday, 29 Nov 2018 at 09:38, Julius Dittmar wrote:
>>> Am 29.11.18 um 09:13 schrieb Julius Dittmar:
>>>> Am 29.11.18 um 08:17 schrieb Loris Bennett:
>>>>>> #+latex_header: \makeatletter\let\mytextheight\beamer@frametexheight\makeatother
>>>>>> #+attr_latex: :height 0.75\mytextheight
>>> Oh, or perhaps just a typo is involved: is it really
>>> \beamer@frametexheight or rather \beamer@frametextheight you are chasing
>>> after?
>> Also, you may need to define your mytextheight as a length and then use \setlength instead of \let.
> After correcting the typo I followed Eric's and Julius's suggestions and
> I tried adding
>
> #+LATEX_HEADER: \newlength\mytextheight\makeatletter\setlength\mytextheight{\beamer@frametextheight}\makeatother
>
> to the beginning of the Org file, but in this case
>
> \the\mytextheight
>
> is 0.0pt. After that I tried adding the definition on the slide itself:
>
> #+BEGIN_SRC latex
> \newlength\mytextheight\makeatletter\setlength\mytextheight{\beamer@frametextheight}\makeatother
> #+END_SRC
>
> but got the error
>
> ! Undefined control sequence.
> <argument> \beamer
>
> l.153 \end{frame}
>
> ! Missing number, treated as zero.
> <to be read again>
> @
> l.153 \end{frame}
>
> Any thoughts?
>
> Cheers,
>
> Loris
>
[-- Attachment #2: Type: text/html, Size: 3112 bytes --]
next prev parent reply other threads:[~2018-11-29 13:24 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 [this message]
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
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=9904e5c3-cfec-458e-426b-2f69b586d570@gmail.com \
--to=gusbrs.2016@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=loris.bennett@fu-berlin.de \
/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).