emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Axel Kielhorn <org-mode@axelkielhorn.de>
To: Org-Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Custom beamer blocks for pros and cons list
Date: Fri, 27 May 2022 09:38:05 +0200	[thread overview]
Message-ID: <31AD6105-91AB-4F1F-B28F-F6528B28CBB0@axelkielhorn.de> (raw)
In-Reply-To: <86o7zk7zep.fsf@gmail.com>


> Am 26.05.2022 um 23:32 schrieb Andrés Ramírez <rrandresf@gmail.com>:
> 

You want something like this as the resulting LaTeX code:

\begin{frame}[label={sec:org5359014}]{Comparisson}
\begin{columns}
\begin{column}{0.45\columnwidth}
\begin{block}{Pros}        % <- superfluous environment
\begin{problock}{Problock} % <— argument required
\begin{itemize}
\item New.
\item Other Pro.
\item Additional Pro.
\end{itemize}
\end{problock}
\end{block}
\end{column}

> #+LaTeX_Header: \newenvironment<>{problock}[1]{%

The =problock= environment takes 1 argument, but you supply none.

You can supply an argument 
#+begin_problock    
@@latex:{Probloc}@@ 

This will be ignored for non-LaTeX exporters.

But even here you have to block environments, the outer environment generated by =*** Pros= and the inner problock environment.

You can get rid of the outer block environment by removing

   :BEAMER_env: block


The resulting org code will look like this:

   :PROPERTIES:
   :BEAMER_col: 0.45
   :END:
#+begin_problock Pros    
@@latex:{Probloc}@@ 
 - New.
 - Other Pro.
 - Additional Pro.
#+end_problock

Greetings
Axel

next prev parent reply	other threads:[~2022-05-27  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 21:32 Custom beamer blocks for pros and cons list Andrés Ramírez
2022-05-27  7:38 ` Axel Kielhorn [this message]
2022-05-27  8:33   ` Ihor Radchenko
2022-05-27 14:15     ` andrés ramírez
2022-05-27 14:13   ` andrés ramírez

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=31AD6105-91AB-4F1F-B28F-F6528B28CBB0@axelkielhorn.de \
    --to=org-mode@axelkielhorn.de \
    --cc=emacs-orgmode@gnu.org \
    /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

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).