From: bob--- via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Emacs Orgmode <emacs-orgmode@gnu.org>
Subject: Implementing ox-beamer property support in ox-latex.
Date: Tue, 21 Jun 2022 14:14:12 +0200 (CEST) [thread overview]
Message-ID: <N554Qia--7-2@vergauwen.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
Dear list,
I recently fell in love with the properties support provided by ox-beamer.
Especially in combination with an appropriate column view, this feature allows you to create complex presentations and maintain a good overview of all slides, layouts and possible transitions.
Today I attempted to implement similar behaviour for ox-latex, with moderate success.
The problem that I encountered was that you can't easily "close" environments.
The example below shows what I mean:
* First section
** First subsection
Some text before the definition.
*** Definition 1
:PROPERTIES:
:LATEX_ENV: definition
:END:
This is a definition
*** This title is ignored and very ugly
:PROPERTIES:
:LATEX_ENV: empty
:END:
Some text behind the definition.
** Subsection
This is a new subsection.
Expands to:
\begin{document}\section{First section}
\subsection{First subsection}
Some text before the definition.
\begin{definition}[Definition 1]
This is a definition
\end{definition}
Some text behind the definition.
\subsection{Subsection}
This is a new subsection.
\end{document}
In order to indicate that the body of definition 1 has endend, I needed to create an empty block which is ignored by the exporter.
Is there an elegant way to solve this problem and to "close" a heading?
Maybe in the form of an alternative carriage return character or a multiple line breaks?
Kind regards,
Bob
[-- Attachment #2: Type: text/html, Size: 2954 bytes --]
next reply other threads:[~2022-06-21 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 12:14 bob--- via General discussions about Org-mode. [this message]
2022-06-22 10:22 ` Implementing ox-beamer property support in ox-latex Fraga, Eric
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=N554Qia--7-2@vergauwen.me \
--to=emacs-orgmode@gnu.org \
--cc=bob@vergauwen.me \
/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).