From: Jarmo Hurri <email@example.com>
Subject: Re: Missing line breaks in Beamer with alltt
Date: Mon, 30 Nov 2020 07:03:31 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Eric S Fraga <email@example.com> writes:
> On Sunday, 29 Nov 2020 at 11:22, Jarmo Hurri wrote:
>> Any ideas?
> First of all, the first frame works just fine for me. Line breaks are
Fascinating: it has to be something in my settings. I went through my
init files and did not find anything relevant. Off to debug I go then.
> When in doubt, export to LaTeX (C-e l b) and have a look at the LaTeX.
> Also then run pdflatex yourself on that LaTeX code to see what errors
> come up.
I did that but did not notice anything weird in the latex code. Then
again, if I export to regular latex, line breaks are preserved just
fine. Therefore, this has to be related to some beamer settings (or my
texlive version or something like that).
Thanks for pointing me in the right direction.
All the best, and stay safe.
next prev parent reply other threads:[~2020-11-30 5:06 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 [this message]
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
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).