From: Jarmo Hurri <email@example.com>
Subject: Re: Missing line breaks in Beamer with alltt
Date: Fri, 04 Dec 2020 16:03:02 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Hi there Eric.
Eric S Fraga <email@example.com> writes:
>> I will take you up on that offer! Are you able to replicate the
>> difference between these two slides?
> Interesting. It seems that the use of =...= in one of the items makes
> org insert the "fragile" option for the frame and that allows the alltt
> environment to work properly. The solution therefore is either make
> sure that there is at least one use of =...= in the slide or, better
> yet, add the fragile option yourself by setting the BEAMER_opt property
> to fragile, as in:
> * Another slide
> :BEAMER_opt: fragile
> I've tested this and it works for me.
Works for me too, excellent!
I have an eerie feeling that this should be either
a) fixed so that it works without inserting fragile, or
b) written down somewhere in documentation.
All the best, and stay safe.
next prev parent reply other threads:[~2020-12-04 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 9:22 Jarmo Hurri
2020-11-29 12:33 ` Eric S Fraga
2020-11-30 5:03 ` Jarmo Hurri
2020-11-30 9:32 ` Eric S Fraga
2020-12-03 16:07 ` Jarmo Hurri
2020-12-03 16:38 ` Eric S Fraga
2020-12-04 14:03 ` Jarmo Hurri [this message]
2020-12-04 15:17 ` Eric S Fraga
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 \
* 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).