From: Uwe Brauer <email@example.com>
Subject: Re: export to babel, sometimes a block environment is inserted.
Date: Fri, 16 Oct 2020 18:06:44 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
>>> "ESF" == Eric S Fraga <email@example.com> writes:
> On Thursday, 15 Oct 2020 at 19:44, Uwe Brauer wrote:
>> How can I avoid this annoying block environment?
> I know you have sort of solved this (by promoting the headline to a
> higher level) but the question I would have asked is: what did you want
> the export engine to do with a subheading?
Well because this is how I would have written it starting directly in Latex.
Subsections help me to organize the documents, so I thought subheadings
would be converted to subsections, without interfering with blocks. So I
have learned something I did not know before.
> In beamer, org assumes that a subheading starts some kind of block and
> the default is just a basic block.
Ok I did not know that. I have to admit I use org mode, either because
of its excellent table editor, or if I want to export text+some code to LaTeX
> You can change this to other types or have org ignore the actual
> headline. I use the latter to provide some structure to the org file
> without affecting the output.
I think I have to learn more about that.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2020-10-16 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 17:44 export to babel, sometimes a block environment is inserted Uwe Brauer
2020-10-15 18:40 ` Colin Baxter
2020-10-15 19:34 ` Uwe Brauer
2020-10-16 8:54 ` Eric S Fraga
2020-10-16 16:06 ` Uwe Brauer [this message]
2020-10-17 11:17 ` Eric S Fraga
2020-10-17 13:26 ` Uwe Brauer
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).